Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 36 21 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 20:14.408 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:26.403
Before features/support/hooks.rb:269 0.004
Given a computer 0.599
And I create a 7200 MiB disk named "old" 0.396
And I plug USB drive "old" 1.303
And I write an old version of the Tails USB image to disk "old" 34.866
When I start Tails from USB drive "old" with network unplugged 1:44.807
Then the boot device has safe access rights 3.336
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:326 7.819
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.279
Before features/support/hooks.rb:269 0.007
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 1:25.459
Then Tails is running from USB drive "old" 0.362
And I create a persistent partition 31.423
And I take note of which tps features are available 2.086
Then a Tails persistence partition exists on USB drive "old" 0.796
And I shutdown Tails and wait for the computer to power off 6.941
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.011
Tags: @product
3:0.955
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.500
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.323
When I write some files expected to persist 3.983
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.263
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.830
And I take note of which tps features are available 0.692
And I shutdown Tails and wait for the computer to power off 4.108
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.221
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.007
Tags: @product
2:39.509
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 11.364
And I log in to a new session 23.317
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.727
And I plug USB drive "to_upgrade" 2.548
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.197
Then the running Tails is installed on USB drive "to_upgrade" 23.263
And I unplug USB drive "to_upgrade" 0.476
And I unplug USB drive "__internal" 0.612
After features/support/hooks.rb:326 2.770
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.975
Before features/support/hooks.rb:269 0.016
Given a computer 0.529
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.304
Then all tps features from the old Tails version are active 1.918
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.946
And the expected persistent files created with the old Tails version are present in the filesystem 1.965
And all persistent directories from the old Tails version have safe access rights 2.953
After features/support/hooks.rb:326 0.656
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
7:3.558
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 15.811
And no SquashFS delta is installed 0.145
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
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.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.150
And Tor is ready 22.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.880
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.012
Given I shutdown Tails and wait for the computer to power off 15.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.072
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.398
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.404
# 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.311
When the network is plugged 0.096
And Tor is ready 23.013
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.145
Given I shutdown Tails and wait for the computer to power off 4.647
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.223
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 3.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.594
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.321
When the network is plugged 0.085
And Tor is ready 17.345
Then the Upgrader considers the system as up-to-date 0.323
# 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 16.575
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.206
After features/support/hooks.rb:326 0.805
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
34.725
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.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 1.489
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 15.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.173
After features/support/hooks.rb:326 0.965
After features/support/hooks.rb:100 0.000