Project Number Date
test_Tails_ISO_stable 5645 13 May 2025, 19:27

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
5:23.138
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.470
And I wait until Tor is ready 4.743
When I disconnect the network through GNOME 3.000
And I connect the network through GNOME 2.870
Then the Tor Connection Assistant autostarts 2.373
And the Tor Connection Assistant connects to Tor 2.258
And I wait until Tor is ready 5:0.419
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:711:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:709:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:662:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.408

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:44)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log

Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/00:31:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:100 0.044
Tags: @product
1:42.999
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.170
And I start Tails from USB drive "usbimage" with network unplugged and I login 1:42.829
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_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:330 5.382

SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:07:59)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/01:07:59_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/01:07:59_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/01:07:59_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/01:07:59_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.journal

After features/support/hooks.rb:100 0.005
Tags: @product
1:43.909
Scenario APT sources are configured correctly
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given a computer 0.277
And I start Tails from DVD with network unplugged 1:43.631
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:263: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:263:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/apt.feature:8:in `And I start Tails from DVD with network unplugged'
Then the only hosts in APT sources are "cloudfront.debian.net,deb.tails.boum.org,deb.torproject.org" 0.000
And no proposed-updates APT suite is enabled 0.000
And no experimental APT suite is enabled for deb.torproject.org 0.000
And if releasing, no unversioned Tails APT source is enabled 0.000
And if releasing, the tagged Tails APT source is enabled 0.000
After features/support/hooks.rb:330 4.921

SCENARIO FAILED: 'APT sources are configured correctly' (at time 02:06:54)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/02:06:54_APT_sources_are_configured_correctly.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/02:06:54_APT_sources_are_configured_correctly.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/02:06:54_APT_sources_are_configured_correctly.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/02:06:54_APT_sources_are_configured_correctly.journal

After features/support/hooks.rb:100 0.010
34.282
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 6.990
And I cancel the GNOME authentication prompt 2.334
And I unlock and mount this VeraCrypt volume with GNOME Disks 24.957
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:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/veracrypt.rb:269: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:330 5.530

SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 05:13:33)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/05:13:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/05:13:33_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/5645/artifact/build-artifacts/05:13:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5645/artifact/build-artifacts/05:13:33_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal

After features/support/hooks.rb:100 0.001