Project Number Date
test_Tails_ISO_stable 4685 28 Feb 2024, 12:18

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
8:6.564
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:245 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8:6.564
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:561:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:516: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/snapshots.rb:148:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:145:in `each'
./features/step_definitions/snapshots.rb:145:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:168:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:76:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
And I wait 20 seconds 0.000
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:291 4.655 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:36:34)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/00:36:34_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/00:36:34_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/00:36:34_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/00:36:34_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:75 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
3:50.164
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:245 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.878
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
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.316
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.032
And Tor is ready 19.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.242
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.112
Given I shutdown Tails and wait for the computer to power off 3:0.112
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:834:in `/^Tails eventually (shuts down|restarts)$/'
./features/step_definitions/common_steps.rb:846:in `/^I shutdown Tails and wait for the computer to power off$/'
features/usb_upgrade.feature:92: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
After features/support/hooks.rb:291 9.596 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:50:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/01:50:24_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/01:50:24_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
After features/support/hooks.rb:75 0.000
Feature: Tails persistence
Tags: @product
3:39.814
Scenario Feature activation fails
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.789
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.088
When I try to enable persistence 0.242
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 25.506
When I log in to a new session after having activated the Persistent Storage 3:5.187
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:561:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:516: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/persistence.feature:147:in `When I log in to a new session after having activated the Persistent Storage'
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000
And all tps features are enabled 0.000
And all tps features but the first one are active 0.000
After features/support/hooks.rb:291 4.666 
SCENARIO FAILED: 'Feature activation fails' (at time 03:22:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/03:22:15_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/03:22:15_Feature_activation_fails.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/03:22:15_Feature_activation_fails.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4685/artifact/build-artifacts/03:22:15_Feature_activation_fails.journal
After features/support/hooks.rb:75 0.000