Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 41 28 Nov 2024, 20:01

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:15.699 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:18.231
Before features/support/hooks.rb:269 0.005
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 32.523
When I start Tails from USB drive "old" with network unplugged 1:40.290
Then the boot device has safe access rights 3.113
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.201
After features/support/hooks.rb:326 3.536
After features/support/hooks.rb:100 0.035
Tags: @product
2:17.546
Before features/support/hooks.rb:269 0.008
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:29.372
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 36.379
And I take note of which tps features are available 2.101
Then a Tails persistence partition exists on USB drive "old" 0.868
And I shutdown Tails and wait for the computer to power off 8.234
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.357
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:17.555
Then Tails is running from USB drive "old" 0.369
And all tps features are active 2.074
When I write some files expected to persist 2.140
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 2.691
And I take note of which tps features are available 0.555
And I shutdown Tails and wait for the computer to power off 4.253
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.893
After features/support/hooks.rb:326 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.257
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 12.038
And I log in to a new session 21.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.180
And I plug USB drive "to_upgrade" 2.418
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.570
Then the running Tails is installed on USB drive "to_upgrade" 23.903
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:326 2.785
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.753
Before features/support/hooks.rb:269 0.006
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.897
Then all tps features from the old Tails version are active 1.618
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.782
And the expected persistent files created with the old Tails version are present in the filesystem 1.546
And all persistent directories from the old Tails version have safe access rights 2.381
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.008
8:6.391
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 13.538
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.328
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.352
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.520
When the network is plugged 0.063
And Tor is ready 20.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.864
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.732
Given I shutdown Tails and wait for the computer to power off 1:19.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.967
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.275
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.360
# 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.297
When the network is plugged 0.075
And Tor is ready 48.494
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.643
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.981
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.740
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.960
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.315
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.355
When the network is plugged 0.107
And Tor is ready 21.471
Then the Upgrader considers the system as up-to-date 0.346
# 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.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.011
After features/support/hooks.rb:326 0.730
After features/support/hooks.rb:100 0.019
39.162
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 10.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.912
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 21.597
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.879
After features/support/hooks.rb:326 0.711
After features/support/hooks.rb:100 0.000