Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 26 11 Nov 2024, 19:37

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.678 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:16.365
Before features/support/hooks.rb:269 0.005
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 29.767
When I start Tails from USB drive "old" with network unplugged 1:41.054
Then the boot device has safe access rights 3.156
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.335
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:326 7.546
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.284
Before features/support/hooks.rb:269 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:24.914
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 31.256
And I take note of which tps features are available 1.559
Then a Tails persistence partition exists on USB drive "old" 0.789
And I shutdown Tails and wait for the computer to power off 8.260
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.008
Tags: @product
2:54.285
Before features/support/hooks.rb:269 0.005
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.161
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.163
When I write some files expected to persist 1.767
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 2.303
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.080
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.139
After features/support/hooks.rb:326 0.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:27.712
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 10.522
And I log in to a new session 19.072
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.437
And I plug USB drive "to_upgrade" 2.533
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.822
Then the running Tails is installed on USB drive "to_upgrade" 17.905
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:326 2.822
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.581
Before features/support/hooks.rb:269 0.007
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.374
Then all tps features from the old Tails version are active 2.209
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 3.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.537
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:326 0.683
After features/support/hooks.rb:100 0.010
7:36.933
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 16.534
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.386
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.086
And Tor is ready 21.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.942
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.414
Given I shutdown Tails and wait for the computer to power off 10.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.954
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.343
# 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.303
When the network is plugged 0.077
And Tor is ready 16.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.687
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.911
Given I shutdown Tails and wait for the computer to power off 59.527
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.849
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.326
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.378
And Tor is ready 17.811
Then the Upgrader considers the system as up-to-date 10.867
# 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.470
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.990
After features/support/hooks.rb:326 0.744
After features/support/hooks.rb:100 0.018
41.514
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 12.661
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.653
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 1.033
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 19.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.353
After features/support/hooks.rb:326 0.768
After features/support/hooks.rb:100 0.000