Project Number Date
test_Tails_ISO_20522-ocr-more 32 17 Jan 2025, 05:26

Failures Overview

The following summary displays scenarios that failed.

Feature: Hardware failures
Tags: @product @doc
20.780
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.193
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.849
When Tails detects disk read failures on the SquashFS 0.497
Then I see a disk failure message 10.240
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:27:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.455 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:04:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
21.285
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.181
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.255
When Tails detects disk read failures on the boot device 0.569
Then I see a disk failure message 10.279
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:28:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.615 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:04:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:04:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
34.375
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.673
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.948
When Tails detects disk read failures on the boot device with a target error 0.460
Then I see a disk failure message 10.292
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.469 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:05:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:05:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:05:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:05:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/02:05:36_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
5.383
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 5.383
Command 
Command failed (returned pid 63043 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/tmp/tails-amd64-20522-ocr-more@77e50ff1b9+stable@a24a050793-20250117T0001Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/tmp/tails-amd64-20522-ocr-more@77e50ff1b9+stable@a24a050793-20250117T0001Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - rsync (3.2.7-1+deb12u2) to Debian trixie (3.3.0+ds1-4)
.
<0> expected but was
<#<Process::Status: pid 63043 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/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: Using persistent Tor bridges and pluggable transports
4:29.053
Background
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 23.141
And I create a persistent partition with the default settings 22.303
Then the "TorConfiguration" tps feature is not enabled 1.207
When the network is plugged 0.080
And the Tor Connection Assistant autostarts 8.769
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 13.097
And I wait until Tor is ready 1.277
Then tca.conf includes the configured bridges 0.012
And the "TorConfiguration" tps feature is enabled and active 1.133
When I cold reboot the computer 9.438
And the computer reboots Tails 1:1.403
And I enable persistence 26.217
And I capture all network traffic 0.006
And I log in to a new session 40.835
Then tca.conf includes the configured bridges 0.013
When the network is plugged 0.113
And the Tor Connection Assistant autostarts 1:0.001
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
features/persistent_tor_bridges.feature:24:in `And the Tor Connection Assistant autostarts'
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 14.223 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 03:46:37)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/03:46:37_Disabling_persistence_of_Tor_bridges_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/03:46:37_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/03:46:37_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/32/artifact/build-artifacts/03:46:37_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.056