Project Number Date
test_Tails_ISO_devel 3764 03 Apr 2025, 14:18

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 39:9.464 Failed
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:4.716
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 30.504
When I start Tails from USB drive "old" with network unplugged 1:29.079
Then the boot device has safe access rights 2.869
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.327
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.585
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:25.238
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 32.549
And I take note of which tps features are available 1.388
Then a Tails persistence partition exists on USB drive "old" 0.882
And I shutdown Tails and wait for the computer to power off 8.226
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.011
Tags: @product
2:52.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.318
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.960
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.422
And I take note of which tps features are available 0.394
And I shutdown Tails and wait for the computer to power off 4.299
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.954
After features/support/hooks.rb:330 0.142
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.583
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 11.330
And I log in to a new session 18.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.873
And I plug USB drive "to_upgrade" 2.344
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.532
Then the running Tails is installed on USB drive "to_upgrade" 20.329
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:330 2.330
After features/support/hooks.rb:100 0.000
Tags: @product
22:7.010
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 22:6.819
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 10.830 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:05:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3764/artifact/build-artifacts/02:05:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3764/artifact/build-artifacts/02:05:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3764/artifact/build-artifacts/02:05:03_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:52.695
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 with a persistent partition enabled and logged in 11.895
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.418
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.063
And Tor is ready 47.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.604
Given I shutdown Tails and wait for the computer to power off 9.185
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.144
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.275
When the network is plugged 0.061
And Tor is ready 20.614
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.972
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.570
Given I shutdown Tails and wait for the computer to power off 4.562
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.234
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.923
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.067
And Tor is ready 16.590
Then the Upgrader considers the system as up-to-date 10.768
# 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.490
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.600
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.232
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 with a persistent partition enabled and logged in 9.888
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.096
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.067
And Tor is ready 16.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.972
After features/support/hooks.rb:330 1.266
After features/support/hooks.rb:100 0.000