Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 19 22 Mar 2025, 06:19

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 18:52.624 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
1:55.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 28.401
When I start Tails from USB drive "old" with network unplugged 1:21.656
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.685
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.768
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:21.477
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 29.503
And I take note of which tps features are available 1.901
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.529
After features/support/hooks.rb:330 0.131
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.478
Then Tails is running from USB drive "old" 0.985
And all tps features are active 3.325
When I write some files expected to persist 2.723
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 2.302
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 4.614
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.747
After features/support/hooks.rb:330 0.095
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.749
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 9.531
And I log in to a new session 16.920
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.499
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.833
Then the running Tails is installed on USB drive "to_upgrade" 17.178
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 2.157
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.983
Then all tps features from the old Tails version are active 1.699
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.200
And the expected persistent files created with the old Tails version are present in the filesystem 1.339
And all persistent directories from the old Tails version have safe access rights 2.198
After features/support/hooks.rb:330 0.959
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:44.927
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.141
And no SquashFS delta is installed 0.237
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.484
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.477
When the network is plugged 0.273
And Tor is ready 21.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.628
Given I shutdown Tails and wait for the computer to power off 8.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.305
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.236
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.263
# 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.261
When the network is plugged 0.069
And Tor is ready 46.228
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.570
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.501
Given I shutdown Tails and wait for the computer to power off 4.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.551
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.068
And Tor is ready 18.873
Then the Upgrader considers the system as up-to-date 0.358
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.831
After features/support/hooks.rb:330 0.854
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
38.646
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 10.153
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.060
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 21.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.507
After features/support/hooks.rb:330 0.767
After features/support/hooks.rb:100 0.000