Project Number Date
test_Tails_ISO_stable 4815 29 Apr 2024, 12:30

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
23.147
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.522
Then the keys trusted by APT are valid for the next 3 months 14.625
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.450 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:20:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:20:15_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:20:15_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:20:15_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:20:15_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Spoofing MAC addresses
Tags: @product
27.128
Scenario MAC address spoofing fails and the module is not removed
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.003
And I capture all network traffic 0.007
And the network is plugged 0.045
And macchanger will fail by not spoofing and always returns true 0.155
And no network interface modules can be unloaded 0.403
When I log in to a new session 18.119
Then 1 network interface is enabled 0.139
But the MAC spoofing panic mode disabled networking 0.252
NetworkManager 
NetworkManager was not disabled.
<false> 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 6.088 
SCENARIO FAILED: 'MAC address spoofing fails and the module is not removed' (at time 02:55:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:55:06_MAC_address_spoofing_fails_and_the_module_is_not_removed.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:55:06_MAC_address_spoofing_fails_and_the_module_is_not_removed.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:55:06_MAC_address_spoofing_fails_and_the_module_is_not_removed.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/02:55:06_MAC_address_spoofing_fails_and_the_module_is_not_removed.journal
After features/support/hooks.rb:89 0.043
Feature: Tails persistence
Tags: @product
1:45.630
Scenario Persistent Greeter options
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 45.278
When I enable persistence 1:0.351
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/usb.rb:655:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:104:in `When I enable persistence'
Then no persistent Greeter options were restored 0.000
When I set all Greeter options to non-default values 0.000
And I log in to a new session in German (de) after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
Given I enable persistence 0.000
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:305 5.718 
SCENARIO FAILED: 'Persistent Greeter options' (at time 03:20:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/03:20:58_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/03:20:58_Persistent_Greeter_options.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/03:20:58_Persistent_Greeter_options.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/03:20:58_Persistent_Greeter_options.journal
After features/support/hooks.rb:89 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
32.677
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 7.218
And I cancel the GNOME authentication prompt 2.063
And I unlock and mount this VeraCrypt volume with GNOME Disks 23.395
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-disks]: child with name="Select a Keyfile" roleName='file chooser'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/veracrypt.rb:280:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:51:in `And I unlock and mount this VeraCrypt volume with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:305 4.554 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 04:36:36)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/04:36:36_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/04:36:36_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/04:36:36_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4815/artifact/build-artifacts/04:36:36_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:89 0.000