Project Number Date
test_Tails_ISO_devel 3291 20 Feb 2024, 21:58

Failures Overview

The following summary displays scenarios that failed.

3:50.722
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:245 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.720
And no SquashFS delta is installed 0.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.369
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.515
When the network is plugged 0.047
And Tor is ready 18.819
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.777
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.440
Given I shutdown Tails and wait for the computer to power off 3:0.395
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.645

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/01:57:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/01:57:44_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

After features/support/hooks.rb:75 0.000
Tags: @product
2:13.923
Scenario Feature activation fails
Before features/support/hooks.rb:245 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.106
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.081
When I try to enable persistence 0.258
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 40.919
When I log in to a new session after having activated the Persistent Storage 1:2.608
Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 20.950
cannot find GnomeActivitiesOverviewSearch.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:1015:in `/^I start "([^"]+)" via GNOME Activities Overview$/'
./features/step_definitions/usb.rb:1687:in `/^the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:148:in `Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated'
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 5.628

SCENARIO FAILED: 'Feature activation fails' (at time 03:38:57)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/03:38:57_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/03:38:57_Feature_activation_fails.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/03:38:57_Feature_activation_fails.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3291/artifact/build-artifacts/03:38:57_Feature_activation_fails.journal

After features/support/hooks.rb:75 0.000