Project Number Date
test_Tails_ISO_devel 3790 28 Apr 2025, 13:55

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
26:38.607
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.013
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.229
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.459
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.267
And the file system changes introduced in version 6.2~testoverlayfs are not present 1.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.088
And Tor is ready 22.852
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.424
Given I shutdown Tails and wait for the computer to power off 11.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.177
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.817
And the file system changes introduced in version 6.2~testoverlayfs are present 0.377
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.348
When the network is plugged 0.076
And Tor is ready 49.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.146
Given I shutdown Tails and wait for the computer to power off 4.294
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:5.422
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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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 10.894 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:15:19)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:15:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.020
Feature: Backing up the persistent storage
Tags: @product
1:21.361
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.263
# 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 11.058
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.906
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.487
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.026
When I start Tails' custom backup tool 7.152
Then the backup tool displays "Plug in your backup Tails USB stick" 0.288
When I plug USB drive "backup" 2.854
And I give the Persistent Storage on drive "backup" its own UUID 0.235
And I click "Retry" in the backup tool 1.237
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.753
When I click "Back Up" in the backup tool 1.203
And I enter my persistent storage passphrase into the polkit prompt 20.893
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/common_steps.rb:791:in `deal_with_polkit_prompt'
./features/step_definitions/backup.rb:18:in `/^I enter my persistent storage passphrase into the polkit prompt$/'
features/backup.feature:21:in `And I enter my persistent storage passphrase into the polkit prompt'
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000
# 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:330 9.624 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 02:24:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:24:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:24:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3790/artifact/build-artifacts/02:24:51_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.154
Feature: Packages are up-to-date
Tags: @source
3.436
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 3.436
Command 
Command failed (returned pid 72807 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@b5dcadb3d0-20250428T0721Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@b5dcadb3d0-20250428T0721Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - linux-signed-amd64[linux-headers-amd64, linux-image-amd64] (6.1.133-1) to Debian bookworm-security (6.1.135+1)
  - linux[linux-compiler-gcc-12-x86] (6.1.133-1) to Debian bookworm-security (6.1.135-1)
  - linux[linux-kbuild-6.1, linux-libc-dev] (6.1.133-1) to Debian bookworm-security (6.1.135-1)
.
<0> expected but was
<#<Process::Status: pid 72807 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/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