Project Number Date
test_Tails_ISO_stable 6331 29 Apr 2026, 07:35

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
1:9.453
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.077
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.007
And I plug USB drive "temp" 1.017
And I write the Tails USB image to disk "temp" 13.228
When I start Tails from USB drive "temp" with network unplugged 54.722
Then Tails is running from USB drive "temp" 0.399
<"usb"> expected but was
<"ata">. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:918:in `/^Tails is running from (.*) drive "([^"]+)"$/'
features/hardware_failure.feature:82:in `Then Tails is running from USB drive "temp"'
features/hardware_failure.feature:73:in `Then Tails is running from USB drive "temp"'
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error fs-not-resized 0.000
After features/support/hooks.rb:331 4.927

SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 01:39:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/01:39:55_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/01:39:55_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/01:39:55_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/01:39:55_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal

After features/support/hooks.rb:100 0.111
0.613
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:544 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.613
Command failed (pid 69087 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@dbe7a11e6d-20260429T0313Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@dbe7a11e6d-20260429T0313Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-04-29 04:05:02+00:00 (1:47:01.934656 ago)
INFO: Need to upgrade to a new APT snapshot:
  - electrum[electrum] (4.7.0+dfsg-1~bpo13+1) to Debian trixie-backports (4.7.2+dfsg-1~bpo13+1)
  - electrum[python3-electrum] (4.7.0+dfsg-1~bpo13+1) to Debian trixie-backports (4.7.2+dfsg-1~bpo13+1)
  - firmware-nonfree (20260309-1) to Debian forky (20260410-1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/step_definitions/needed_package_updates.rb:10:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:13:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:551 0.000
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.966
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.882
And a web server is running on the LAN 1.026
And I capture all network traffic 0.005
When I start the Tor Browser 14.005
And I open a page on the LAN web server in the Tor Browser 4.046
Then the Tor Browser shows the "Unable to connect" error 1:0.000
try_for() timeout expired (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/browser.rb:383:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:13:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:331 5.406

SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 03:23:21)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/03:23:21_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/03:23:21_The_Tor_Browser_cannot_access_the_LAN.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/03:23:21_The_Tor_Browser_cannot_access_the_LAN.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6331/artifact/build-artifacts/03:23:21_The_Tor_Browser_cannot_access_the_LAN.journal

After features/support/hooks.rb:100 0.041