Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 32 04 Apr 2025, 07:03

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:49.076 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:3.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.239
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 31.158
When I start Tails from USB drive "old" with network unplugged 1:27.091
Then the boot device has safe access rights 3.012
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.276
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:330 6.991
After features/support/hooks.rb:100 0.008
Tags: @product
2:6.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:24.170
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 30.676
And I take note of which tps features are available 2.281
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:330 0.187
After features/support/hooks.rb:100 0.008
Tags: @product
3:26.751
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.236
Then Tails is running from USB drive "old" 0.425
And all tps features are active 6.858
When I write some files expected to persist 1.684
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.230
And all persistence configuration files have safe access rights 0.403
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 2.845
And I shutdown Tails and wait for the computer to power off 6.489
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.024
After features/support/hooks.rb:330 0.135
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.012
And I log in to a new session 20.773
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.758
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.111
Then the running Tails is installed on USB drive "to_upgrade" 27.898
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:330 3.544
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.943
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.272
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.082
Then all tps features from the old Tails version are active 1.950
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.513
After features/support/hooks.rb:330 0.915
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:13.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.899
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.091
And Tor is ready 23.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.428
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.619
Given I shutdown Tails and wait for the computer to power off 8.692
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.427
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.387
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.292
When the network is plugged 0.100
And Tor is ready 18.492
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.824
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.951
Given I shutdown Tails and wait for the computer to power off 6.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.376
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.311
And the file system changes introduced in version 6.3~testoverlayfs are present 0.648
And only the 6.3~testoverlayfs SquashFS delta is installed 0.112
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.294
When the network is plugged 0.089
And Tor is ready 20.089
Then the Upgrader considers the system as up-to-date 0.313
# 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.681
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.474
After features/support/hooks.rb:330 0.721
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
37.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.104
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 16.812
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.247
After features/support/hooks.rb:330 1.958
After features/support/hooks.rb:100 0.000