Project Number Date
test_Tails_ISO_test-suite-options 13 29 Jun 2025, 20:59

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 25:6.051 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:53.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.273
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 39.518
When I start Tails from USB drive "old" with network unplugged 2:4.231
Then the boot device has safe access rights 6.722
And Tails is running from USB drive "old" 0.483
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.261
After features/support/hooks.rb:330 3.768
After features/support/hooks.rb:100 0.009
Tags: @product
3:0.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 1:58.852
Then Tails is running from USB drive "old" 0.445
And I create a persistent partition 43.675
And I take note of which tps features are available 4.121
Then a Tails persistence partition exists on USB drive "old" 2.498
And I shutdown Tails and wait for the computer to power off 10.259
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
1:51.328
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.249
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.078
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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.776 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:55:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/01:55:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Tags: @product
3:22.089
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 without a persistent partition and stopped at Tails Greeter's login screen 14.620
And I log in to a new session 28.125
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.209
And I plug USB drive "to_upgrade" 3.102
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:54.234
Then the running Tails is installed on USB drive "to_upgrade" 38.335
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:330 3.284
After features/support/hooks.rb:100 0.000
Tags: @product
3:35.688
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.030
Steps
Given a computer 0.332
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:27.034
Then all tps features from the old Tails version are active 3.715
And Tails is running from USB drive "to_upgrade" 0.674
And the boot device has safe access rights 3.872
And the expected persistent files created with the old Tails version are present in the filesystem 0.059
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1097:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1096:in `each'
./features/step_definitions/usb.rb:1096:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 6.420 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:02:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-options/13/artifact/build-artifacts/02:02:20_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
9:32.618
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 18.933
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.271
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.492
When the network is plugged 0.105
And Tor is ready 28.718
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.784
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.045
Given I shutdown Tails and wait for the computer to power off 15.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:0.631
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.536
And the file system changes introduced in version 6.2~testoverlayfs are present 0.462
And only the 6.2~testoverlayfs SquashFS delta is installed 0.113
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.414
When the network is plugged 0.090
And Tor is ready 28.426
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.122
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.631
Given I shutdown Tails and wait for the computer to power off 6.836
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.777
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.484
And the file system changes introduced in version 6.3~testoverlayfs are present 0.644
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.335
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.401
When the network is plugged 0.075
And Tor is ready 29.092
Then the Upgrader considers the system as up-to-date 0.930
# 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 23.677
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.018
After features/support/hooks.rb:330 0.665
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
51.170
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 13.820
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.100
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.209
And the signing key used by the Upgrader is outdated 0.289
But a current signing key is available on our website 0.000
When the network is plugged 0.178
And Tor is ready 23.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.204
After features/support/hooks.rb:330 4.028
After features/support/hooks.rb:100 0.000