Cucumber Reports (no 5178) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5178	12 Oct 2024, 12:38

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

5:36.099

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 14.758

And no SquashFS delta is installed 0.211

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

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

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

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

When the network is plugged 0.115

And Tor is ready 25.993

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

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

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

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

cannot

cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:559:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:515:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:295: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

Hooks

After features/support/hooks.rb:326 5.086

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:51:53)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/01:51:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.025

Feature: Packages are up-to-date

Tags: @source

3.506

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 3.506

Command

Command failed (returned pid 83525 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@e474ac8d56-20241012T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@e474ac8d56-20241012T0716Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-sof (2023.12.1-1.1) to Debian trixie (2024.06-1)
  - gdisk (1.0.10-1~bpo12+1~tails1) to Debian trixie (1.0.10-2)
  - intel-microcode (3.20240813.2) to Debian trixie (3.20240910.1)
  - onioncircuits (0.8.1-1) to Debian trixie (0.8.1-2)
  - ublock-origin (1.57.0+dfsg-1) to Debian trixie (1.60.0+dfsg-1)
.
<0> expected but was
<#<Process::Status: pid 83525 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'

Hooks

After features/support/hooks.rb:539 0.000

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

8:1.986

Scenario Playing an Ogg audio track

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.813

When I start the Tor Browser 22.164

And the Tor Browser loads the startup page 0.814

Then I can listen to an Ogg audio track in Tor Browser 7:26.194

Tor

Tor operation failed (despite retrying 10 times) with
Test::Unit::AssertionFailedError: <false> is not true. (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/browser.rb:355:in `/^I can listen to an Ogg audio track in Tor Browser$/'
features/torified_browsing.feature:41:in `Then I can listen to an Ogg audio track in Tor Browser'

Hooks

After features/support/hooks.rb:515 0.051

After features/support/hooks.rb:326 5.546

Output 1

SCENARIO FAILED: 'Playing an Ogg audio track' (at time 04:15:22)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/04:15:22_Playing_an_Ogg_audio_track.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/04:15:22_Playing_an_Ogg_audio_track.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/04:15:22_Playing_an_Ogg_audio_track.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5178/artifact/build-artifacts/04:15:22_Playing_an_Ogg_audio_track.journal

After features/support/hooks.rb:100 0.000