Cucumber Reports (no 3279) - Failures Overview

Project	Number	Date
test_Tails_ISO_devel	3279	13 Feb 2024, 22:11

Feature: Additional software

4:46.890

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

Before features/support/hooks.rb:442 0.006

Steps

Given a computer 0.269

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 4:46.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:554:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:509: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:294: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/additional_software_packages.feature:75:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'

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

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

And I accept adding "cowsay" to Additional Software 0.000

And Additional Software is correctly configured for package "cowsay" 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

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

And the network is plugged 0.000

And Tor is ready 0.000

# 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 0.000

And available upgrades have been checked 0.000

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

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

After features/support/hooks.rb:291 4.971

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:29:58)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_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_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:29:58_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:75 0.008

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

7:44.842

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:245 0.005

Before features/support/hooks.rb:442 0.004

Steps

Given a computer 0.191

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

And I enable persistence 31.154

And I remove the "cowsay" deb files from the APT cache 0.678

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.087

And I log in to a new session 1:13.352

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.288

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

And I can open the Additional Software log file from the notification 0.000

And the package "cowsay" is not installed 0.000

Hooks

After features/support/hooks.rb:450 0.034

After features/support/hooks.rb:291 7.947

Output 1

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:37:48)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:37:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:37:48_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

After features/support/hooks.rb:75 0.010

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

3:57.539

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:245 0.007

Steps

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

And no SquashFS delta is installed 0.116

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

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

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

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

When the network is plugged 0.058

And Tor is ready 19.750

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

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

Given I shutdown Tails and wait for the computer to power off 3:0.431

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:843:in `/^Tails eventually (shuts down|restarts)$/'
./features/step_definitions/common_steps.rb:855:in `/^I shutdown Tails and wait for the computer to power off$/'
features/usb_upgrade.feature:93:in `Given I shutdown Tails and wait for the computer to power off'

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.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:291 9.561

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:55:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:55:12_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

After features/support/hooks.rb:75 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

22.058

Scenario Tails erases memory on DVD boot medium removal: vfat

Hooks

Before features/support/hooks.rb:245 0.008

Steps

Given I have started Tails from DVD without network and logged in 7.972

And I prepare Tails for memory erasure tests 0.406

And I plug and mount a 128 MiB USB drive with a vfat filesystem 7.817

And I fill the USB drive with a known pattern 2.085

And I read the content of the test FS 0.100

And patterns cover at least 99% of the test FS size in the guest's memory 3.675

98.981%

98.981% of the test FS size (127.599609375 MiB) has the pattern, but more than 99.000% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:170:in `/^patterns cover at least (\d+)% of the test FS size in the guest's memory$/'
features/emergency_shutdown.feature:31:in `And patterns cover at least 99% of the test FS size in the guest's memory'

Output 1

Pattern coverage: 98.981% (126 MiB out of 127 MiB reference memory)

When I eject the boot medium 0.000

And I wait for Tails to finish wiping the memory 0.000

Then I find very few patterns in the guest's memory 0.000

Hooks

After features/support/hooks.rb:291 4.234

Output 1

SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: vfat' (at time 01:57:54)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:57:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:57:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:57:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3279/artifact/build-artifacts/01:57:54_Tails_erases_memory_on_DVD_boot_medium_removal:_vfat.journal

After features/support/hooks.rb:75 0.000