Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 11 15 Mar 2025, 07:15

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow
36:54.247
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:511 0.004
Steps
Given a computer 0.184
And I start Tails from USB drive "__internal" and I login with an administration password 1:54.049
And I update APT using apt 35:0.014
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/misc_helpers.rb:180:in `new'
./features/support/helpers/misc_helpers.rb:180:in `force_new_tor_circuit'
./features/support/helpers/misc_helpers.rb:192:in `block in retry_tor'
./features/support/helpers/misc_helpers.rb:222:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:59:in `/^I update APT using apt$/'
features/additional_software_packages.feature:47:in `And I update APT using apt'
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:519 0.053
After features/support/hooks.rb:330 10.827 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:43:14)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/01:43:14_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/01:43:14_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/01:43:14_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
21:59.277
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.005
Steps
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 21:59.064
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: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 10.821 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:28:03)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/02:28:03_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_20816-block-paths-bwrap/11/artifact/build-artifacts/02:28:03_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_20816-block-paths-bwrap/11/artifact/build-artifacts/02:28:03_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
2:1.727
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.005
Steps
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.138
Then all tps features from the old Tails version are active 1.589
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.368
And the expected persistent files created with the old Tails version are present in the filesystem 0.094
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 5.668 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:32:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/02:32:48_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_20816-block-paths-bwrap/11/artifact/build-artifacts/02:32:48_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/02:32:48_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/02:32:48_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.018
Feature: Tails persistence
Tags: @product
1:47.789
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.037
And the network is plugged 0.090
And Tor is ready 19.100
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.180
And I shutdown Tails and wait for the computer to power off 8.428
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.951
try_for() 
try_for() timeout expired (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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/usb.rb:672:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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/persistence.feature:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 4.959 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 04:11:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/04:11:30_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/04:11:30_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/04:11:30_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/11/artifact/build-artifacts/04:11:30_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.008