Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 31 27 Nov 2024, 21:12

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
23:18.495
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 26.683
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.384
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.069
And Tor is ready 18.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.166
Given I shutdown Tails and wait for the computer to power off 10.991
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:1.249
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:712:in `new'
./features/step_definitions/common_steps.rb:712: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:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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:326 10.828 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:07:12)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/31/artifact/build-artifacts/02:07:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.009
Feature: Packages are up-to-date
Tags: @source
3.595
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 3.595
Command 
Command failed (returned pid 57868 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@babfdf7182+stable@22c5d86462-20241127T1537Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@babfdf7182+stable@22c5d86462-20241127T1537Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - blinker (1.8.2-1) to Debian trixie (1.9.0-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.1-1)
.
<0> expected but was
<#<Process::Status: pid 57868 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/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