Project Number Date
test_Tails_ISO_devel 3483 17 Aug 2024, 12:32

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
5:25.035
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.695
And I wait until Tor is ready 4.182
When I disconnect the network through GNOME 2.936
And I connect the network through GNOME 3.234
Then the Tor Connection Assistant autostarts 2.899
And the Tor Connection Assistant connects to Tor 4.707
And I wait until Tor is ready 5:0.378
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:707:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:705:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:658: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:326 5.149

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

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_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_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/00:32:24_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:100 0.044
Tags: @source
0.186
Scenario All packages are up-to-date
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 0.186
Command failed (returned pid 54723 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@d969b9ae16-20240817T0657Z.build-manifest", {:err=>[:child, :out]}]:
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 417, in <module>
    main()
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 386, in main
    suites = tuple(get_suites(config.get("distribution")))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", line 334, in get_suites
    codename_pos = ddi_s.index(min_codename)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: 'bullseye' is not in list
.
<0> expected but was
<#<Process::Status: pid 54723 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Random Seed
Tags: @product
2:38.200
Scenario A random seed is read during boot and written during boot and shutdown
Before features/support/hooks.rb:269 0.011
Steps
Given a computer 0.260
And I temporarily create a 7200 MiB disk named "temp" 0.055
And I plug USB drive "temp" 1.054
And I write the Tails USB image to disk "temp" 31.153
Then there is no random seed on USB drive "temp" 6.045
When I start Tails from USB drive "temp" with network unplugged 1:59.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:454: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:453:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:287: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:453:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:287: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/random_seed.feature:13:in `When I start Tails from USB drive "temp" with network unplugged'
Then the random seed was written multiple times on first boot 0.000
And there is a random seed on USB drive "temp" 0.000
When I log in to a new session 0.000
And I wait for the random seed to be updated 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Then there is a random seed on USB drive "temp" 0.000
And the random seed is different from the previous one 0.000
After features/support/hooks.rb:326 5.368

SCENARIO FAILED: 'A random seed is read during boot and written during boot and shutdown' (at time 03:58:17)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/03:58:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/03:58:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/03:58:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3483/artifact/build-artifacts/03:58:17_A_random_seed_is_read_during_boot_and_written_during_boot_and_shutdown.journal

After features/support/hooks.rb:100 0.118