Project Number Date
test_Tails_ISO_stable 5364 02 Jan 2025, 12:17

Failures Overview

The following summary displays scenarios that failed.

Feature: Backing up the persistent storage
Tags: @product
1:13.360
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.391
# 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 8.457
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.346
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.888
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.025
When I start Tails' custom backup tool 3.658
Then the backup tool displays "Plug in your backup Tails USB stick" 0.285
When I plug USB drive "backup" 2.632
And I give the Persistent Storage on drive "backup" its own UUID 0.137
And I click "Retry" in the backup tool 1.147
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.254
When I click "Back Up" in the backup tool 1.121
And I enter my persistent storage passphrase into the polkit prompt 1.998
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 30.015
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "zenity" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/backup.rb:7:in `new'
./features/step_definitions/backup.rb:7: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/backup.rb:6: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/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.187 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:56:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/01:56:51_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/5364/artifact/build-artifacts/01:56:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/01:56:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/01:56:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.135
Feature: Packages are up-to-date
Tags: @source
13.867
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 13.867
Command 
Command failed (returned pid 70274 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@05d403c596-20250102T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@05d403c596-20250102T0716Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20240610-1) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-brcm80211, firmware-ipw2x00, firmware-libertas, firmware-intel-graphics, firmware-intel-sound, firmware-atheros, firmware-amd-graphics, firmware-intel-misc, firmware-iwlwifi] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-misc-nonfree, firmware-nvidia-graphics, firmware-mediatek, firmware-linux, firmware-realtek, firmware-linux-nonfree] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-ti-connectivity] (20240909-2) to Debian trixie (20241210-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.2-1)
.
<0> expected but was
<#<Process::Status: pid 70274 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
Feature: Tails persistence
Tags: @product
1:56.948
Scenario Dotfiles persistence
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.633
When I write some dotfile expected to persist 0.085
And I shutdown Tails and wait for the computer to power off 9.023
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.204
try_for() 
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:451: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:450:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/persistence.feature:139:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:326 4.852 
SCENARIO FAILED: 'Dotfiles persistence' (at time 03:17:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/03:17:24_Dotfiles_persistence.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/03:17:24_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/03:17:24_Dotfiles_persistence.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5364/artifact/build-artifacts/03:17:24_Dotfiles_persistence.journal
After features/support/hooks.rb:100 0.011