Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 3 06 Mar 2025, 01:38

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 20:23.869 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:33.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 34.484
When I start Tails from USB drive "old" with network unplugged 1:53.263
Then the boot device has safe access rights 3.364
And Tails is running from USB drive "old" 0.595
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:330 3.635
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.409
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login 1:34.198
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 33.060
And I take note of which tps features are available 2.062
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 8.705
After features/support/hooks.rb:330 0.366
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.601
Then Tails is running from USB drive "old" 0.349
And all tps features are active 2.183
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.237
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.688
And I take note of which tps features are available 0.841
And I shutdown Tails and wait for the computer to power off 4.259
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.554
After features/support/hooks.rb:330 0.132
After features/support/hooks.rb:100 0.008
Tags: @product
2:38.871
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 12.502
And I log in to a new session 20.135
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.676
And I plug USB drive "to_upgrade" 2.578
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.392
Then the running Tails is installed on USB drive "to_upgrade" 24.143
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 6.626
After features/support/hooks.rb:100 0.000
Tags: @product
2:29.007
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:18.950
Then all tps features from the old Tails version are active 1.846
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.711
After features/support/hooks.rb:330 1.108
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:47.582
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 13.890
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.610
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.127
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.508
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.240
And Tor is ready 22.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.638
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.563
Given I shutdown Tails and wait for the computer to power off 8.950
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.492
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.346
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.247
When the network is plugged 0.076
And Tor is ready 17.959
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.359
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.454
Given I shutdown Tails and wait for the computer to power off 4.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.395
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.036
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
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.320
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.078
And Tor is ready 19.220
Then the Upgrader considers the system as up-to-date 0.331
# 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.514
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:330 0.771
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.801
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.552
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.127
But a current signing key is available on our website 0.000
When the network is plugged 0.097
And Tor is ready 18.930
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.400
After features/support/hooks.rb:330 0.736
After features/support/hooks.rb:100 0.000