Project Number Date
test_Tails_ISO_devel 3840 28 May 2025, 09:59

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 80 1 6 0 0 87 6 1 7 21:0.223 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:42.857
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Steps
Given a computer 0.259
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.723
When I start Tails from USB drive "old" with network unplugged 2:8.768
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 5.103 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 01:36:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3840/artifact/build-artifacts/01:36:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3840/artifact/build-artifacts/01:36:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3840/artifact/build-artifacts/01:36:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3840/artifact/build-artifacts/01:36:11_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.264
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:30.583
Then Tails is running from USB drive "old" 0.394
And I create a persistent partition 31.224
And I take note of which tps features are available 2.406
Then a Tails persistence partition exists on USB drive "old" 0.810
And I shutdown Tails and wait for the computer to power off 8.653
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.012
Tags: @product
2:55.586
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.337
Then Tails is running from USB drive "old" 0.463
And all tps features are active 2.041
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.313
And all persistence configuration files have safe access rights 0.683
And all persistent directories from the old Tails version have safe access rights 2.923
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 6.363
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.145
After features/support/hooks.rb:330 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.280
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 without a persistent partition and stopped at Tails Greeter's login screen 11.652
And I log in to a new session 19.169
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.721
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.643
Then the running Tails is installed on USB drive "to_upgrade" 25.201
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 2.316
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.993
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.119
Then all tps features from the old Tails version are active 1.883
And Tails is running from USB drive "to_upgrade" 0.365
And the boot device has safe access rights 3.414
And the expected persistent files created with the old Tails version are present in the filesystem 1.403
And all persistent directories from the old Tails version have safe access rights 2.593
After features/support/hooks.rb:330 0.935
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:27.733
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 26.658
And no SquashFS delta is installed 0.192
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.330
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.580
When the network is plugged 0.103
And Tor is ready 20.879
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.845
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.542
Given I shutdown Tails and wait for the computer to power off 8.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.978
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.366
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.287
When the network is plugged 0.096
And Tor is ready 43.881
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.653
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.609
Given I shutdown Tails and wait for the computer to power off 4.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.279
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.528
And the file system changes introduced in version 6.3~testoverlayfs are present 0.552
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.308
When the network is plugged 0.288
And Tor is ready 17.916
Then the Upgrader considers the system as up-to-date 0.312
# 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 16.376
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.913
After features/support/hooks.rb:330 0.794
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.507
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.807
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.506
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.131
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 18.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.399
After features/support/hooks.rb:330 1.511
After features/support/hooks.rb:100 0.000