Project Number Date
test_Tails_ISO_stable 5264 14 Nov 2024, 12:49

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:22.441
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 9.002
And I wait until Tor is ready 1.599
When I disconnect the network through GNOME 3.014
And I connect the network through GNOME 3.004
Then the Tor Connection Assistant autostarts 2.182
And the Tor Connection Assistant connects to Tor 3.369
And I wait until Tor is ready 5:0.267
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:704:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:702:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:655: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.322 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/00:32:45_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/5264/artifact/build-artifacts/00:32:45_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/5264/artifact/build-artifacts/00:32:45_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/00:32:45_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/00:32:45_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/00:32:45_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/00:32:45_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.040
Feature: Backing up the persistent storage
Tags: @product
1:27.693
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.782
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 10.934
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.612
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.355
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.120
When I start Tails' custom backup tool 4.465
Then the backup tool displays "Plug in your backup Tails USB stick" 0.780
When I plug USB drive "backup" 2.906
And I give the Persistent Storage on drive "backup" its own UUID 0.266
And I click "Retry" in the backup tool 1.606
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.201
When I click "Back Up" in the backup tool 1.198
And I enter my persistent storage passphrase into the polkit prompt 6.437
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.024
try_for() 
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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:326 7.559 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:06:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/02:06:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/02:06:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/02:06:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5264/artifact/build-artifacts/02:06:56_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.179
Feature: Packages are up-to-date
Tags: @source
14.672
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 14.672
Command 
Command failed (returned pid 54162 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@60885f7e53-20241114T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@60885f7e53-20241114T0716Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - base-files (12.4+deb12u7) to Debian bookworm (12.4+deb12u8)
  - cjson (1.7.15-1+deb12u1) to Debian bookworm (1.7.15-1+deb12u2)
  - curl[curl] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - curl[libcurl3-gnutls, libcurl4] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - distro-info-data (0.58+deb12u2) to Debian bookworm (0.58+deb12u3)
  - glib2.0 (2.74.6-2+deb12u3) to Debian bookworm (2.74.6-2+deb12u4)
  - glibc[libc6, libc-bin, libc6-dev, libc-l10n, libc-dev-bin] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - glibc[locales] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - gtk+3.0[gir1.2-gtk-3.0, gtk-update-icon-cache] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - gtk+3.0[libgtk-3-common, libgtk-3-bin, libgtk-3-0] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - intel-microcode (3.20240813.1~deb12u1) to Debian bookworm (3.20240910.1~deb12u1)
  - iputils (3:20221126-1) to Debian bookworm (3:20221126-1+deb12u1)
  - ntfs-3g[libntfs-3g89] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - ntfs-3g[ntfs-3g] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - python-cryptography (38.0.4-3) to Debian bookworm (38.0.4-3+deb12u1)
  - sqlite3 (3.40.1-2) to Debian bookworm (3.40.1-2+deb12u1)
  - systemd[libnss-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libpam-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libsystemd-shared, libudev1, libsystemd0, libudev-dev] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[systemd-sysv, udev, systemd, systemd-oomd, systemd-timesyncd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
.
<0> expected but was
<#<Process::Status: pid 54162 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/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