Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 35 20 Nov 2024, 20:22

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 21:58.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:41.512
Before features/support/hooks.rb:269 0.008
Given a computer 0.671
And I create a 7200 MiB disk named "old" 0.207
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 57.845
When I start Tails from USB drive "old" with network unplugged 1:37.157
Then the boot device has safe access rights 3.424
And Tails is running from USB drive "old" 0.407
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.602
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.441
Before features/support/hooks.rb:269 0.004
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login 1:27.713
Then Tails is running from USB drive "old" 0.360
And I create a persistent partition 32.958
And I take note of which tps features are available 2.183
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 9.048
After features/support/hooks.rb:326 0.247
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.194
Before features/support/hooks.rb:269 0.004
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.458
Then Tails is running from USB drive "old" 0.528
And all tps features are active 2.178
When I write some files expected to persist 1.922
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.253
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.792
And I take note of which tps features are available 0.516
And I shutdown Tails and wait for the computer to power off 4.393
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.453
After features/support/hooks.rb:326 0.339
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.506
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.224
And I log in to a new session 19.647
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.043
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.948
Then the running Tails is installed on USB drive "to_upgrade" 18.738
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.251
After features/support/hooks.rb:326 2.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.530
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.790
Then all tps features from the old Tails version are active 1.999
And Tails is running from USB drive "to_upgrade" 0.470
And the boot device has safe access rights 4.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.688
And all persistent directories from the old Tails version have safe access rights 2.930
After features/support/hooks.rb:326 0.704
After features/support/hooks.rb:100 0.008
8:34.894
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.012
And no SquashFS delta is installed 0.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.339
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.475
When the network is plugged 0.086
And Tor is ready 20.603
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.301
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.033
Given I shutdown Tails and wait for the computer to power off 1:39.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.252
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 2.550
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
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.341
# 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.338
When the network is plugged 0.084
And Tor is ready 47.058
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.590
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.674
Given I shutdown Tails and wait for the computer to power off 4.317
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.502
Then Tails is running version 6.3~testoverlayfs 0.033
And all tps features are active 2.374
And the file system changes introduced in version 6.3~testoverlayfs are present 0.551
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.466
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.379
When the network is plugged 0.087
And Tor is ready 19.519
Then the Upgrader considers the system as up-to-date 0.359
# 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.970
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.137
After features/support/hooks.rb:326 0.776
After features/support/hooks.rb:100 0.014
39.790
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.618
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.115
And the signing key used by the Upgrader is outdated 0.949
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 19.940
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.936
After features/support/hooks.rb:326 1.292
After features/support/hooks.rb:100 0.000