Cucumber Reports (no 4621) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4621	16 Jan 2024, 18:55

Feature: Additional software

11:49.086

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:245 0.007

Before features/support/hooks.rb:442 0.007

Steps

Given a computer 0.264

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:13.414

And I configure APT to prefer an old version of cowsay 0.027

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 23.718

And I accept adding "cowsay" to Additional Software 1:6.106

And Additional Software is correctly configured for package "cowsay" 1.554

And I shutdown Tails and wait for the computer to power off 6.070

And I start Tails from USB drive "__internal" with network unplugged 47.013

And I enable persistence 31.342

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.023

And I log in to a new session 25.450

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.238

And I revert the APT tweaks that made it prefer an old version of cowsay 0.082

# We remove the newest package after it has been downloaded and before

# it is installed, so that the upgrade process fails

And I prepare the Additional Software upgrade process to fail 0.106

And the network is plugged 0.043

And Tor is ready 19.988

# Note: the next step races against the appearance of the "The

# upgrade of your additional software failed" notification.

# It should win most of the time, which is good, but there's no

# guarantee it does. If it loses, then it'll remove the notification

# we'll be trying to interact with below ("I can open…")

And all notifications have disappeared 10.284

And available upgrades have been checked 0.365

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 5:1.991

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:548:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:101:in `And I see the "The upgrade of your additional software failed" notification after at most 300 seconds'

And I can open the Additional Software configuration window from the notification 0.000

And I shutdown Tails and wait for the computer to power off 0.000

And I start Tails from USB drive "__internal" with network unplugged 0.000

And I enable persistence 0.000

# We need to add back this custom APT source for the Additional Software

# install step, as it was not saved in persistence

And I configure APT to prefer an old version of cowsay 0.000

And I log in to a new session 0.000

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000

And I revert the APT tweaks that made it prefer an old version of cowsay 0.000

And the network is plugged 0.000

And Tor is ready 0.000

Then the Additional Software upgrade service has started 0.000

And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000

Hooks

After features/support/hooks.rb:450 0.042

After features/support/hooks.rb:291 7.477

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:32:31)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:32:31_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:32:31_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

After features/support/hooks.rb:75 0.026

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

5:20.516

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:245 0.005

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.092

And no SquashFS delta is installed 0.073

And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 1.512

And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083

And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.353

And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.554

When the network is plugged 0.740

And Tor is ready 17.620

Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.677

And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.933

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

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

cannot

cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:166:in `rescue in wait'
./features/support/helpers/screen.rb:159:in `wait'
./features/step_definitions/common_steps.rb:499:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:454: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:240: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 2.2~testoverlayfsng 0.000

And all tps features are active 0.000

And the file system changes introduced in version 2.2~testoverlayfsng are present 0.000

And only the 2.2~testoverlayfsng 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_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng 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 2.3~testoverlayfsng 0.000

And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 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 2.3~testoverlayfsng 0.000

And all tps features are active 0.000

And the file system changes introduced in version 2.3~testoverlayfsng are present 0.000

And only the 2.3~testoverlayfsng 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 2.1~testoverlayfsng 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 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 0.000

Hooks

After features/support/hooks.rb:291 4.816

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:50:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:50:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:50:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4621/artifact/build-artifacts/01:50:38_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:75 0.011