Cucumber Reports (no 4630) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4630	23 Jan 2024, 13:36

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

7:43.935

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 10.208

And no SquashFS delta is installed 0.147

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

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

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

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

When the network is plugged 0.044

And Tor is ready 15.434

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

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

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

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

Then Tails is running version 2.2~testoverlayfsng 0.125

And all tps features are active 2.159

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

And only the 2.2~testoverlayfsng 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.312

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

When the network is plugged 0.033

And Tor is ready 15.047

Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.972

And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.863

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

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

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:546:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:501: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:286: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 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.893

Output 1

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

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

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

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

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

After features/support/hooks.rb:75 0.019