Cucumber Reports (no 44) - Failures Overview

Project	Number	Date
test_Tails_ISO_20530-tca-controls-tor-flag-file	44	10 Dec 2024, 22:20

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

26:0.429

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

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 12.717

And no SquashFS delta is installed 0.115

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.419

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.545

When the network is plugged 0.062

And Tor is ready 19.416

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.452

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.025

Given I shutdown Tails and wait for the computer to power off 13.988

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.341

Then Tails is running version 6.2~testoverlayfs 0.018

And all tps features are active 2.551

And the file system changes introduced in version 6.2~testoverlayfs are present 0.371

And only the 6.2~testoverlayfs SquashFS delta is installed 0.088

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.332

# 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.321

When the network is plugged 0.080

And Tor is ready 17.155

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.556

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.092

Given I shutdown Tails and wait for the computer to power off 6.437

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:59.914

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: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

Hooks

After features/support/hooks.rb:326 10.890

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:13:49)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/44/artifact/build-artifacts/02:13:49_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/44/artifact/build-artifacts/02:13:49_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/44/artifact/build-artifacts/02:13:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.019

Feature: Packages are up-to-date

Tags: @source

14.641

Scenario All packages are up-to-date

Hooks

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.640

Command

Command failed (returned pid 53507 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@d31e2b2102+stable@9f1104ca3a-20241210T1630Z.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@d31e2b2102+stable@9f1104ca3a-20241210T1630Z.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)
  - flask (3.0.3-1) to Debian trixie (3.1.0-2)
  - python-werkzeug (3.0.4-1) to Debian trixie (3.1.3-2)
.
<0> expected but was
<#<Process::Status: pid 53507 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'

Hooks

After features/support/hooks.rb:539 0.000

After features/support/hooks.rb:100 0.000