Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 11 12 Mar 2025, 01:02

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:27.435 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:20.443
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 32.797
When I start Tails from USB drive "old" with network unplugged 1:41.926
Then the boot device has safe access rights 3.273
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.383
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.587
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.501
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:28.238
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 33.370
And I take note of which tps features are available 2.166
Then a Tails persistence partition exists on USB drive "old" 0.840
And I shutdown Tails and wait for the computer to power off 9.352
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.012
Tags: @product
3:0.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.266
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.580
Then Tails is running from USB drive "old" 0.505
And all tps features are active 2.485
When I write some files expected to persist 2.190
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.424
And all persistent directories from the old Tails version have safe access rights 2.473
And I take note of which tps features are available 0.494
And I shutdown Tails and wait for the computer to power off 4.421
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.840
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.840
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.717
And I log in to a new session 19.441
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.033
And I plug USB drive "to_upgrade" 2.556
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.351
Then the running Tails is installed on USB drive "to_upgrade" 25.277
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.252
After features/support/hooks.rb:330 1.961
After features/support/hooks.rb:100 0.000
Tags: @product
2:33.508
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.031
Then all tps features from the old Tails version are active 1.861
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.787
And the expected persistent files created with the old Tails version are present in the filesystem 1.608
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:330 1.429
After features/support/hooks.rb:100 0.010
7:0.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.219
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.621
When the network is plugged 0.061
And Tor is ready 21.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.054
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.830
Given I shutdown Tails and wait for the computer to power off 11.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.480
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.122
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.286
When the network is plugged 0.082
And Tor is ready 20.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.669
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.916
Given I shutdown Tails and wait for the computer to power off 6.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.710
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.071
And Tor is ready 16.773
Then the Upgrader considers the system as up-to-date 10.892
# 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.777
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.944
After features/support/hooks.rb:330 0.968
After features/support/hooks.rb:100 0.024
41.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.137
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 22.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.864
After features/support/hooks.rb:330 0.690
After features/support/hooks.rb:100 0.000