Project Number Date
test_Tails_ISO_stable 5611 29 Apr 2025, 21:17

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 19:11.335 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:20.748
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.341
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 31.865
When I start Tails from USB drive "old" with network unplugged 1:42.720
Then the boot device has safe access rights 3.551
And Tails is running from USB drive "old" 0.401
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.143
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:330 3.778
After features/support/hooks.rb:100 0.013
Tags: @product
2:15.577
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login 1:34.686
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 30.077
And I take note of which tps features are available 2.624
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 6.785
After features/support/hooks.rb:330 0.203
After features/support/hooks.rb:100 0.011
Tags: @product
1:41.036
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.007
Steps
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.840
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 4.983 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:38:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5611/artifact/build-artifacts/01:38:27_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_stable/5611/artifact/build-artifacts/01:38:27_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_stable/5611/artifact/build-artifacts/01:38:27_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_stable/5611/artifact/build-artifacts/01:38:27_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.012
Tags: @product
2:41.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.353
And I log in to a new session 22.340
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.658
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.058
Then the running Tails is installed on USB drive "to_upgrade" 28.476
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:330 0.912
After features/support/hooks.rb:100 0.000
Tags: @product
2:31.756
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.006
Steps
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:25.139
Then all tps features from the old Tails version are active 2.305
And Tails is running from USB drive "to_upgrade" 0.460
And the boot device has safe access rights 3.562
And the expected persistent files created with the old Tails version are present in the filesystem 0.070
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.019 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:43:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5611/artifact/build-artifacts/01:43:46_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_stable/5611/artifact/build-artifacts/01:43:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5611/artifact/build-artifacts/01:43:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5611/artifact/build-artifacts/01:43:46_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:2.987
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.875
And no SquashFS delta is installed 0.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.384
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.517
When the network is plugged 0.087
And Tor is ready 23.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.956
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.868
Given I shutdown Tails and wait for the computer to power off 9.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:20.335
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.560
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.414
# 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.305
When the network is plugged 0.070
And Tor is ready 20.234
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.808
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.846
Given I shutdown Tails and wait for the computer to power off 4.554
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.458
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.396
And the file system changes introduced in version 6.3~testoverlayfs are present 0.568
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.327
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.114
And Tor is ready 20.081
Then the Upgrader considers the system as up-to-date 0.439
# 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.239
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.965
After features/support/hooks.rb:330 0.686
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.433
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.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 19.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.454
After features/support/hooks.rb:330 1.893
After features/support/hooks.rb:100 0.000