Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 27 27 Mar 2025, 21:55

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 19:47.969 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:3.528
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.180
When I start Tails from USB drive "old" with network unplugged 1:27.904
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.107
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 3.502
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:29.971
Then Tails is running from USB drive "old" 0.307
And I create a persistent partition 33.860
And I take note of which tps features are available 1.847
Then a Tails persistence partition exists on USB drive "old" 0.782
And I shutdown Tails and wait for the computer to power off 8.310
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.012
Tags: @product
3:2.892
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.034
Then Tails is running from USB drive "old" 0.412
And all tps features are active 2.717
When I write some files expected to persist 2.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 3.760
And I take note of which tps features are available 0.702
And I shutdown Tails and wait for the computer to power off 6.452
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.357
After features/support/hooks.rb:330 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.772
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.322
And I log in to a new session 19.951
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.500
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.395
Then the running Tails is installed on USB drive "to_upgrade" 24.758
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:330 0.795
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.138
Then all tps features from the old Tails version are active 1.644
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.286
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 2.645
After features/support/hooks.rb:330 1.459
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.582
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.340
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.429
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.070
And Tor is ready 26.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.747
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.832
Given I shutdown Tails and wait for the computer to power off 10.766
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.631
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.239
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.439
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.090
And Tor is ready 20.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.641
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.454
Given I shutdown Tails and wait for the computer to power off 4.299
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.154
Then Tails is running version 6.3~testoverlayfs 0.150
And all tps features are active 2.419
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.274
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.067
And Tor is ready 19.470
Then the Upgrader considers the system as up-to-date 0.329
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 14.813
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.240
After features/support/hooks.rb:330 0.825
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
40.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.844
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.101
And Tor is ready 23.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.546
After features/support/hooks.rb:330 0.695
After features/support/hooks.rb:100 0.000