Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 30 15 Nov 2024, 20:10

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:45.000 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:24.489
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.059
And I write an old version of the Tails USB image to disk "old" 36.928
When I start Tails from USB drive "old" with network unplugged 1:41.718
Then the boot device has safe access rights 3.399
And Tails is running from USB drive "old" 0.394
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:326 3.738
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.248
Before features/support/hooks.rb:269 0.005
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:30.482
Then Tails is running from USB drive "old" 0.450
And I create a persistent partition 32.589
And I take note of which tps features are available 1.687
Then a Tails persistence partition exists on USB drive "old" 0.975
And I shutdown Tails and wait for the computer to power off 8.838
After features/support/hooks.rb:326 0.214
After features/support/hooks.rb:100 0.010
Tags: @product
2:53.389
Before features/support/hooks.rb:269 0.007
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.344
Then Tails is running from USB drive "old" 0.531
And all tps features are active 2.254
When I write some files expected to persist 1.919
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.316
And all persistence configuration files have safe access rights 0.648
And all persistent directories from the old Tails version have safe access rights 2.657
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.397
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.531
After features/support/hooks.rb:326 0.145
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.695
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.539
And I log in to a new session 20.262
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.644
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.951
Then the running Tails is installed on USB drive "to_upgrade" 24.476
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.543
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.110
Before features/support/hooks.rb:269 0.006
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.748
Then all tps features from the old Tails version are active 1.725
And Tails is running from USB drive "to_upgrade" 0.390
And the boot device has safe access rights 3.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.500
And all persistent directories from the old Tails version have safe access rights 2.922
After features/support/hooks.rb:326 0.640
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
6:40.111
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 17.543
And no SquashFS delta is installed 1.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.490
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.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.084
And Tor is ready 23.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.582
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.485
Given I shutdown Tails and wait for the computer to power off 10.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.341
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.393
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.410
# 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.299
When the network is plugged 0.074
And Tor is ready 22.308
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.747
Given I shutdown Tails and wait for the computer to power off 6.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.521
Then Tails is running version 6.3~testoverlayfs 0.045
And all tps features are active 2.188
And the file system changes introduced in version 6.3~testoverlayfs are present 0.566
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.334
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.068
And Tor is ready 22.345
Then the Upgrader considers the system as up-to-date 0.315
# 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.749
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.117
After features/support/hooks.rb:326 0.674
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
37.957
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 11.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.906
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 17.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.862
After features/support/hooks.rb:326 1.869
After features/support/hooks.rb:100 0.000