Project Number Date
test_Tails_ISO_18530-do-not-restart-tor 2 08 Nov 2024, 10:35

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:29.983 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:41.694
Before features/support/hooks.rb:269 0.004
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 49.906
When I start Tails from USB drive "old" with network unplugged 1:44.679
Then the boot device has safe access rights 3.529
And Tails is running from USB drive "old" 0.516
And there is no persistence partition on USB drive "old" 0.112
And process "udev-watchdog" is running 0.177
And udev-watchdog is monitoring the correct device 1.139
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:326 7.299
After features/support/hooks.rb:100 0.010
Tags: @product
2:21.802
Before features/support/hooks.rb:269 0.005
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:32.315
Then Tails is running from USB drive "old" 0.427
And I create a persistent partition 35.660
And I take note of which tps features are available 5.284
Then a Tails persistence partition exists on USB drive "old" 1.052
And I shutdown Tails and wait for the computer to power off 6.818
After features/support/hooks.rb:326 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
3:2.447
Before features/support/hooks.rb:269 0.008
Given a computer 0.826
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.323
Then Tails is running from USB drive "old" 1.066
And all tps features are active 2.013
When I write some files expected to persist 1.759
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.257
And all persistence configuration files have safe access rights 0.448
And all persistent directories from the old Tails version have safe access rights 3.800
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 4.486
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.940
After features/support/hooks.rb:326 0.162
After features/support/hooks.rb:100 0.007
Tags: @product
2:41.034
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.604
And I log in to a new session 22.334
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.724
And I plug USB drive "to_upgrade" 2.571
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.750
Then the running Tails is installed on USB drive "to_upgrade" 24.548
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 4.016
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.022
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.598
Then all tps features from the old Tails version are active 2.086
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 4.609
And the expected persistent files created with the old Tails version are present in the filesystem 1.622
And all persistent directories from the old Tails version have safe access rights 2.548
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:36.865
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.796
And no SquashFS delta is installed 0.512
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.482
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.514
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.443
When the network is plugged 0.080
And Tor is ready 18.675
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.244
Given I shutdown Tails and wait for the computer to power off 11.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.366
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.344
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.289
When the network is plugged 0.072
And Tor is ready 17.310
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.482
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.525
Given I shutdown Tails and wait for the computer to power off 4.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.393
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.360
And the file system changes introduced in version 6.3~testoverlayfs are present 0.556
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.367
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.067
And Tor is ready 16.080
Then the Upgrader considers the system as up-to-date 0.333
# 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.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.036
After features/support/hooks.rb:326 1.090
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
40.117
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.649
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.934
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.646
After features/support/hooks.rb:326 0.798
After features/support/hooks.rb:100 0.000