Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 1 25 Oct 2024, 14:51

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:12.764 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:13.793
Before features/support/hooks.rb:269 0.004
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 38.330
When I start Tails from USB drive "old" with network unplugged 1:30.152
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.345
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.305
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:326 3.769
After features/support/hooks.rb:100 0.010
Tags: @product
2:6.849
Before features/support/hooks.rb:269 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:21.678
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 34.329
And I take note of which tps features are available 1.358
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.204
After features/support/hooks.rb:326 0.191
After features/support/hooks.rb:100 0.009
Tags: @product
2:54.277
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.557
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.090
When I write some files expected to persist 2.206
# 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.383
And all persistent directories from the old Tails version have safe access rights 2.771
And I take note of which tps features are available 0.394
And I shutdown Tails and wait for the computer to power off 4.580
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.491
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.222
Before features/support/hooks.rb:269 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 13.715
And I log in to a new session 18.484
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.862
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.521
Then the running Tails is installed on USB drive "to_upgrade" 21.755
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 3.057
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.402
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.243
Then all tps features from the old Tails version are active 1.782
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.262
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 3.043
After features/support/hooks.rb:326 0.632
After features/support/hooks.rb:100 0.010
6:31.943
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 28.342
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.580
When the network is plugged 0.071
And Tor is ready 21.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.842
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.338
Given I shutdown Tails and wait for the computer to power off 8.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.958
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.158
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.301
When the network is plugged 0.066
And Tor is ready 20.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.680
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.310
Given I shutdown Tails and wait for the computer to power off 4.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.480
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.130
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.329
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.082
And Tor is ready 17.933
Then the Upgrader considers the system as up-to-date 0.365
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.878
After features/support/hooks.rb:326 0.782
After features/support/hooks.rb:100 0.022
35.274
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.435
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.186
And the signing key used by the Upgrader is outdated 1.008
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 18.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.311
After features/support/hooks.rb:326 0.818
After features/support/hooks.rb:100 0.000