Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 5 06 Mar 2025, 15:27

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:4.542 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.668
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 28.918
When I start Tails from USB drive "old" with network unplugged 1:29.523
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.206
After features/support/hooks.rb:330 3.511
After features/support/hooks.rb:100 0.009
Tags: @product
2:8.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:24.424
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 32.336
And I take note of which tps features are available 1.679
Then a Tails persistence partition exists on USB drive "old" 0.932
And I shutdown Tails and wait for the computer to power off 8.412
After features/support/hooks.rb:330 0.200
After features/support/hooks.rb:100 0.008
Tags: @product
2:51.833
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.226
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.522
Then Tails is running from USB drive "old" 0.746
And all tps features are active 2.028
When I write some files expected to persist 1.765
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.481
And all persistent directories from the old Tails version have safe access rights 3.657
And I take note of which tps features are available 0.441
And I shutdown Tails and wait for the computer to power off 6.575
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.128
After features/support/hooks.rb:330 0.103
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.206
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 10.719
And I log in to a new session 19.350
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.134
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.919
Then the running Tails is installed on USB drive "to_upgrade" 21.248
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 6.800
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.410
Then all tps features from the old Tails version are active 1.604
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.408
And the expected persistent files created with the old Tails version are present in the filesystem 1.591
And all persistent directories from the old Tails version have safe access rights 2.403
After features/support/hooks.rb:330 1.191
After features/support/hooks.rb:100 0.011
6:34.258
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.205
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.071
And Tor is ready 18.450
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.735
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.532
Given I shutdown Tails and wait for the computer to power off 8.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.247
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.200
And the file system changes introduced in version 6.2~testoverlayfs are present 0.369
And only the 6.2~testoverlayfs SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.363
# 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.590
When the network is plugged 0.116
And Tor is ready 20.803
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.210
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.259
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.155
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.645
And the file system changes introduced in version 6.3~testoverlayfs are present 0.583
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.295
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.317
When the network is plugged 0.097
And Tor is ready 19.569
Then the Upgrader considers the system as up-to-date 0.315
# 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 15.543
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:330 0.827
After features/support/hooks.rb:100 0.018
37.317
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 10.131
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 20.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.341
After features/support/hooks.rb:330 1.075
After features/support/hooks.rb:100 0.000