Project Number Date
test_Tails_ISO_20816-block-paths-bwrap 12 16 Mar 2025, 07:25

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:53.406
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 10.265
And I wait until Tor is ready 28.348
When I disconnect the network through GNOME 2.858
And I connect the network through GNOME 2.830
Then the Tor Connection Assistant autostarts 2.323
And the Tor Connection Assistant connects to Tor 6.488
And I wait until Tor is ready 5:0.293
Time 
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.199 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:33:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_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_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/00:33:17_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.036
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:8.453
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.768
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.610
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.502
When the network is plugged 0.185
And Tor is ready 21.250
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.298
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.232
Given I shutdown Tails and wait for the computer to power off 8.890
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:4.933
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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 11.061 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:17:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/02:17:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.010
Feature: Packages are up-to-date
Tags: @source
11.036
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:536 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 11.036
Command 
Command failed (returned pid 54595 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/tmp/tails-amd64-20816-block-paths-bwrap@31e70a1ada+stable@bd799e67cd-20250316T0058Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/tmp/tails-amd64-20816-block-paths-bwrap@31e70a1ada+stable@bd799e67cd-20250316T0058Z.build-manifest
ERROR: tor-geoipdb: the package version(0.4.8.14-1+tpo1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
ERROR: tor: the package version(0.4.8.14-1+tpo1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
INFO: Need to upgrade to a new APT snapshot:
  - base-files (12.4+deb12u9) to Debian bookworm (12.4+deb12u10)
  - curl[curl] (7.88.1-10+deb12u8) to Debian bookworm (7.88.1-10+deb12u12)
  - curl[libcurl3-gnutls, libcurl4] (7.88.1-10+deb12u8) to Debian bookworm (7.88.1-10+deb12u12)
  - glibc[libc-dev-bin, libc6, libc-bin, libc6-dev, libc-l10n] (2.36-9+deb12u9) to Debian bookworm (2.36-9+deb12u10)
  - glibc[locales] (2.36-9+deb12u9) to Debian bookworm (2.36-9+deb12u10)
  - intel-microcode (3.20241112.1~deb12u1) to Debian bookworm (3.20250211.1~deb12u1)
  - jinja2 (3.1.2-1+deb12u1) to Debian bookworm (3.1.2-1+deb12u2)
  - librabbitmq (0.11.0-1+b1) to Debian bookworm (0.11.0-1+deb12u1)
  - mozc[ibus-mozc] (2.28.4715.102+dfsg-2.2) to Debian bookworm (2.28.4715.102+dfsg-2.2+deb12u1)
  - mozc[mozc-data, mozc-server] (2.28.4715.102+dfsg-2.2) to Debian bookworm (2.28.4715.102+dfsg-2.2+deb12u1)
  - systemd[libnss-systemd, libpam-systemd] (252.33-1~deb12u1) to Debian bookworm (252.36-1~deb12u1)
  - systemd[libsystemd0, libsystemd-shared, libudev-dev, libudev1] (252.33-1~deb12u1) to Debian bookworm (252.36-1~deb12u1)
  - systemd[systemd, systemd-sysv, systemd-oomd, systemd-timesyncd] (252.33-1~deb12u1) to Debian bookworm (252.36-1~deb12u1)
  - systemd[udev] (252.33-1~deb12u1) to Debian bookworm (252.36-1~deb12u1)
  - tzdata (2024b-0+deb12u1) to Debian bookworm (2025a-0+deb12u1)
  - vim[vim-common, vim-tiny] (2:9.0.1378-2) to Debian bookworm (2:9.0.1378-2+deb12u2)
  - vim[xxd] (2:9.0.1378-2) to Debian bookworm (2:9.0.1378-2+deb12u2)
  - wget (1.21.3-1+b2) to Debian bookworm (1.21.3-1+deb12u1)
.
<0> expected but was
<#<Process::Status: pid 54595 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20816-block-paths-bwrap/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:543 0.000
After features/support/hooks.rb:100 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
22:57.645
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 11.192
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.373
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.398
When I accept the autoconfiguration wizard's configuration 22:45.680
The 
The Dogtail init script raised: SearchError: descendent of [frame | Account Setup - Mozilla Thunderbird]: "Get Messages" button
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:272:in `button'
./features/step_definitions/thunderbird.rb:128:in `/^I fetch my email$/'
./features/step_definitions/thunderbird.rb:160:in `/^I accept the (?:autoconfiguration wizard's|manual) configuration$/'
features/thunderbird.feature:22:in `When I accept the autoconfiguration wizard's configuration'
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
After features/support/hooks.rb:519 0.049
After features/support/hooks.rb:330 5.356 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 05:04:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/05:04:46_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/05:04:46_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/05:04:46_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20816-block-paths-bwrap/12/artifact/build-artifacts/05:04:46_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000