Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 76 05 Jan 2025, 21:08

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
4:49.573
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.245
And I wait until Tor is ready 2.934
When I disconnect the network through GNOME 2.715
And I connect the network through GNOME 2.993
Then the Tor Connection Assistant autostarts 2.460
And the Tor Connection Assistant connects to Tor 2.157
And I wait until Tor is ready 4:30.066
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:261:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:692:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:654: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.103 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:30:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:30:16_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.034
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
1:1.631
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.614
And I prepare Tails for memory erasure tests 0.547
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 52.468
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:784:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1486:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/erase_memory.feature:50:in `When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
Then I find very few patterns in the guest's memory 0.000
# write cache
When I fill the USB drive with a known pattern 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
After features/support/hooks.rb:326 5.271 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:35:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:35:03_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:35:03_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:35:03_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/00:35:03_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.002
Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:15.338
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.442
And I power off the computer 0.338
And the computer is set to boot in UEFI mode 0.034
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.522
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuGRUB_Bullseye.png", "TailsBootMenuGRUB_Bookworm.png"] on the screen
./features/support/helpers/screen.rb:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224:in `wait_any'
./features/step_definitions/common_steps.rb:407:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (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:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:326 10.598 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:02:42)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:02:42_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:02:42_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:02:42_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.075
Feature: Upgrading an old Tails USB installation
Tags: @product
3:17.041
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.767
And I log in to a new session 3:5.274
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:559:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:515: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/usb_upgrade.feature:62:in `And I log in to a new session'
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.000
And I plug USB drive "to_upgrade" 0.000
When I upgrade Tails to USB drive "to_upgrade" by cloning 0.000
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:326 5.349 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:48:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:08_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Feature: Upgrading an old Tails USB installation
Tags: @product
0.236
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.027
Call 
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'to_upgrade' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416:in `set_disk_boot'
./features/step_definitions/common_steps.rb:144:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:282: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
Hooks
After features/support/hooks.rb:326 4.335
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:449:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:444:in `each'
./features/support/hooks.rb:444:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:48:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:13_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/01:48:13_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
3.505
Scenario All packages are up-to-date
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 3.505
Command 
Command failed (returned pid 61546 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@2ed2993d97+stable@05d403c596-20250105T1535Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@2ed2993d97+stable@05d403c596-20250105T1535Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20240610-1) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-iwlwifi, firmware-intel-misc, firmware-libertas, firmware-intel-graphics, firmware-intel-sound, firmware-amd-graphics, firmware-ipw2x00, firmware-brcm80211, firmware-atheros] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-realtek, firmware-mediatek, firmware-misc-nonfree, firmware-linux, firmware-nvidia-graphics, firmware-linux-nonfree] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-ti-connectivity] (20240909-2) to Debian trixie (20241210-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.2-1)
.
<0> expected but was
<#<Process::Status: pid 61546 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
22:57.914
Scenario Persistent browser bookmarks
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 11.652
And all tps features are active 2.335
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.407
And all persistent directories have safe access rights 2.774
When I start the Tor Browser in offline mode 20.944
And I add a bookmark to eff.org in the Tor Browser 11.411
And I cold reboot the computer 13.888
And the computer reboots Tails 1:1.544
And I enable persistence 14.212
And I log in to a new session 38.276
And all notifications have disappeared 20:0.228
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/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
features/torified_browsing.feature:160:in `And all notifications have disappeared'
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:326 10.899 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 04:42:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/04:42:06_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/04:42:06_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/76/artifact/build-artifacts/04:42:06_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:100 0.009