Project Number Date
test_Tails_ISO_devel 3572 31 Oct 2024, 15:48

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:23.605
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 8.616
And I wait until Tor is ready 2.322
When I disconnect the network through GNOME 3.041
And I connect the network through GNOME 2.919
Then the Tor Connection Assistant autostarts 2.451
And the Tor Connection Assistant connects to Tor 3.922
And I wait until Tor is ready 5:0.331
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:704:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:702:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:655:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 5.262 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:26)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/00:32:26_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.051
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
3:7.466
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.238
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.293
And Tor is ready 25.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.992
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.664
Given I shutdown Tails and wait for the computer to power off 9.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.502
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/usb.rb:721:in `greeter_language'
./features/step_definitions/usb.rb:689:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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 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:326 5.542 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:03:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.010
Feature: Tails persistence
Tags: @product
1:11.689
Scenario Feature activation fails
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 11.289
And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.123
When I try to enable persistence 0.263
Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 1:0.014
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/usb.rb:1725:in `/^the Welcome Screen tells me that the Persistent Folder feature couldn't be activated$/'
features/persistence.feature:146:in `Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated'
When I log in to a new session after having activated the Persistent Storage 0.000
And all notifications have disappeared 0.000
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:326 8.550 
SCENARIO FAILED: 'Feature activation fails' (at time 03:45:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/03:45:21_Feature_activation_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/03:45:21_Feature_activation_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/03:45:21_Feature_activation_fails.journal
After features/support/hooks.rb:100 0.000