Project Number Date
test_Tails_ISO_stable 4805 22 Apr 2024, 13:56

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product
22:2.043
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:259 0.008
Steps
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:1.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:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295: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:305 9.881 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:02:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:02:39_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/4805/artifact/build-artifacts/02:02:39_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
After features/support/hooks.rb:89 0.018
Feature: Upgrading an old Tails USB installation
Tags: @product
2:24.343
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.009
Steps
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.801
Then all tps features from the old Tails version are active 2.059
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.858
And the expected persistent files created with the old Tails version are present in the filesystem 0.073
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:22:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1045:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1044:in `each'
./features/step_definitions/usb.rb:1044: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:305 5.446 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:07:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:07:41_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:07:41_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:07:41_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:07:41_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.013
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.155
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.354
Then the keys trusted by APT are valid for the next 3 months 13.800
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.228 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:40:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:40:36_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:40:36_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:40:36_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/02:40:36_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Spoofing MAC addresses
Tags: @product
1:56.065
Scenario MAC address spoofing fails and the module is not removed
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.285
And I capture all network traffic 0.022
And the network is plugged 0.048
And macchanger will fail by not spoofing and always returns true 0.173
And no network interface modules can be unloaded 0.434
When I log in to a new session 1:46.664
Then 1 network interface is enabled 0.138
But the MAC spoofing panic mode disabled networking 0.297
NetworkManager 
NetworkManager was not disabled.
<nil> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/mac_spoofing.rb:94:in `/^the MAC spoofing panic mode disabled networking$/'
features/mac_spoofing.feature:63:in `But the MAC spoofing panic mode disabled networking'
And no network device leaked the real MAC address 0.000
And I see the "All networking disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:305 4.090 
SCENARIO FAILED: 'MAC address spoofing fails and the module is not removed' (at time 03:16:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/03:16:15_MAC_address_spoofing_fails_and_the_module_is_not_removed.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/03:16:15_MAC_address_spoofing_fails_and_the_module_is_not_removed.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/03:16:15_MAC_address_spoofing_fails_and_the_module_is_not_removed.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4805/artifact/build-artifacts/03:16:15_MAC_address_spoofing_fails_and_the_module_is_not_removed.journal
After features/support/hooks.rb:89 0.039