Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 14 14 Mar 2025, 22:44

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:31.645 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:11.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 29.886
When I start Tails from USB drive "old" with network unplugged 1:35.897
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.240
After features/support/hooks.rb:330 3.672
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.022
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.277
And I start Tails from USB drive "old" with network unplugged and I login 1:34.621
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 35.720
And I take note of which tps features are available 1.695
Then a Tails persistence partition exists on USB drive "old" 0.831
And I shutdown Tails and wait for the computer to power off 8.522
After features/support/hooks.rb:330 0.173
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.960
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.577
Then Tails is running from USB drive "old" 0.507
And all tps features are active 2.115
When I write some files expected to persist 1.831
# 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.420
And all persistent directories from the old Tails version have safe access rights 2.590
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.416
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.574
After features/support/hooks.rb:330 0.098
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.664
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 10.960
And I log in to a new session 19.557
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.714
And I plug USB drive "to_upgrade" 2.520
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.163
Then the running Tails is installed on USB drive "to_upgrade" 22.291
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.232
After features/support/hooks.rb:330 1.559
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.460
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:4.647
Then all tps features from the old Tails version are active 1.829
And Tails is running from USB drive "to_upgrade" 0.415
And the boot device has safe access rights 3.558
And the expected persistent files created with the old Tails version are present in the filesystem 1.415
And all persistent directories from the old Tails version have safe access rights 2.392
After features/support/hooks.rb:330 1.617
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
7:35.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.568
And no SquashFS delta is installed 0.436
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.462
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.205
When the network is plugged 0.290
And Tor is ready 20.764
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.953
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.380
Given I shutdown Tails and wait for the computer to power off 1:19.849
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.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.310
When the network is plugged 0.064
And Tor is ready 19.832
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.475
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.185
Given I shutdown Tails and wait for the computer to power off 4.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.856
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.297
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.092
And Tor is ready 19.185
Then the Upgrader considers the system as up-to-date 0.404
# 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.576
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.963
After features/support/hooks.rb:330 0.720
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
35.355
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.330
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.492
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.104
And the signing key used by the Upgrader is outdated 0.089
But a current signing key is available on our website 0.000
When the network is plugged 0.102
And Tor is ready 17.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.503
After features/support/hooks.rb:330 2.366
After features/support/hooks.rb:100 0.000