Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 13 31 Oct 2024, 22:42

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:10.320 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:12.582
Before features/support/hooks.rb:269 0.004
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.533
When I start Tails from USB drive "old" with network unplugged 1:35.139
Then the boot device has safe access rights 3.571
And Tails is running from USB drive "old" 0.346
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 7.487
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.997
Before features/support/hooks.rb:269 0.005
Given a computer 0.204
And I start Tails from USB drive "old" with network unplugged and I login 1:25.873
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 35.391
And I take note of which tps features are available 1.989
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.351
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
3:2.932
Before features/support/hooks.rb:269 0.004
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.599
Then Tails is running from USB drive "old" 0.414
And all tps features are active 2.116
When I write some files expected to persist 2.696
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.275
And all persistence configuration files have safe access rights 1.127
And all persistent directories from the old Tails version have safe access rights 3.101
And I take note of which tps features are available 0.426
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" 24.579
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.007
Tags: @product
2:37.361
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.803
And I log in to a new session 21.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.691
And I plug USB drive "to_upgrade" 2.555
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.614
Then the running Tails is installed on USB drive "to_upgrade" 24.892
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 2.188
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.786
Before features/support/hooks.rb:269 0.006
Given a computer 0.251
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.193
Then all tps features from the old Tails version are active 1.917
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.856
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.576
After features/support/hooks.rb:326 0.577
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:5.724
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 14.458
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.343
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.530
When the network is plugged 0.092
And Tor is ready 53.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.573
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.739
Given I shutdown Tails and wait for the computer to power off 10.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.458
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.397
And only the 6.2~testoverlayfs SquashFS delta is installed 0.117
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.506
# 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.342
When the network is plugged 0.215
And Tor is ready 20.525
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.457
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.346
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.444
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.534
And only the 6.3~testoverlayfs SquashFS delta is installed 0.105
# 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.503
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.457
When the network is plugged 0.089
And Tor is ready 19.721
Then the Upgrader considers the system as up-to-date 0.339
# 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.676
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.115
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
40.935
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 10.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.578
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.841
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 21.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.072
After features/support/hooks.rb:326 0.761
After features/support/hooks.rb:100 0.000