Project Number Date
test_Tails_ISO_20263-test-suite-without-spice 20 27 Mar 2025, 03:19

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow
36:41.125
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Before features/support/hooks.rb:511 0.005
Steps
Given a computer 0.208
And I start Tails from USB drive "__internal" and I login with an administration password 1:40.902
And I update APT using apt 35:0.014
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/misc_helpers.rb:180:in `new'
./features/support/helpers/misc_helpers.rb:180:in `force_new_tor_circuit'
./features/support/helpers/misc_helpers.rb:192:in `block in retry_tor'
./features/support/helpers/misc_helpers.rb:222:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:59:in `/^I update APT using apt$/'
features/additional_software_packages.feature:47:in `And I update APT using apt'
When I install "makepp" using apt 0.000
Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 0.000
And the package "makepp" is installed 0.000
After features/support/hooks.rb:519 0.037
After features/support/hooks.rb:330 10.759 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:40:04)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/01:40:04_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/01:40:04_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/01:40:04_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
7:55.165
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.466
And no SquashFS delta is installed 0.411
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.686
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.700
When the network is plugged 0.083
And Tor is ready 48.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.271
Given I shutdown Tails and wait for the computer to power off 8.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.745
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 2.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.332
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.254
When the network is plugged 0.082
And Tor is ready 18.489
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.709
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.736
Given I shutdown Tails and wait for the computer to power off 6.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.316
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.643
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.265
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.086
And Tor is ready 16.592
Then the Upgrader considers the system as up-to-date 0.304
# 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 1:14.256
cannot 
cannot find UnsafeBrowserStartPage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:78:in `/^I successfully start the Unsafe Browser(?: in "([^"]+)")?$/'
features/usb_upgrade.feature:122:in `And I successfully start the Unsafe Browser'
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:330 7.191 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:16:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/02:16:45_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_20263-test-suite-without-spice/20/artifact/build-artifacts/02:16:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/02:16:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/02:16:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.016
Feature: The Tor enforcement is effective
Tags: @product
1:29.222
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.113
And I capture all network traffic 0.009
When I successfully start the Unsafe Browser 1:17.099
cannot 
cannot find UnsafeBrowserStartPage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/unsafe_browser.rb:63:in `/^the Unsafe Browser shows a warning as its start page$/'
./features/step_definitions/unsafe_browser.rb:71:in `/^the Unsafe Browser has started$/'
./features/step_definitions/browser.rb:78:in `/^I successfully start the Unsafe Browser(?: in "([^"]+)")?$/'
features/tor_enforcement.feature:18:in `When I successfully start the Unsafe Browser'
And I open the Tails homepage in the Unsafe Browser 0.000
And the Tails homepage loads in the Unsafe Browser 0.000
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:330 5.926 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 04:35:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:35:46_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:35:46_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:35:46_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:35:46_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:100 0.048
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
3:34.190
Scenario The Tor Browser's "New identity" feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:511 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.878
When I start the Tor Browser 22.303
And the Tor Browser loads the startup page 3:0.008
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/browser.rb:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:502:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:83:in `And the Tor Browser loads the startup page'
And I open the Tails homepage in the Tor Browser 0.000
Then the Tor Browser loads the Tails homepage 0.000
When I request a new identity in Tor Browser 0.000
Then the Tor Browser restarts into a fresh session 0.000
After features/support/hooks.rb:519 0.035
After features/support/hooks.rb:330 5.638 
SCENARIO FAILED: 'The Tor Browser's "New identity" feature works as expected' (at time 04:51:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:51:05_The_Tor_Browser_s__New_identity__feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:51:05_The_Tor_Browser_s__New_identity__feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:51:05_The_Tor_Browser_s__New_identity__feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-test-suite-without-spice/20/artifact/build-artifacts/04:51:05_The_Tor_Browser_s__New_identity__feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000