Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 12 05 Nov 2024, 12:20

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:50.269
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.358
And I wait until Tor is ready 32.093
When I disconnect the network through GNOME 2.733
And I connect the network through GNOME 2.813
Then the Tor Connection Assistant autostarts 2.778
And the Tor Connection Assistant connects to Tor 3.061
And I wait until Tor is ready 5:0.430
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.249 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:01)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_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_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/00:31:01_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.044
Feature: Upgrading an old Tails USB installation
Tags: @product
1:36.880
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 1:36.689
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:451:in `block (2 levels) in <top (required)>'
./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:450: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:450: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_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:326 4.873 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:40:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:40:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:40:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:40:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:40:11_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
1:22.271
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.008
Steps
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:22.090
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:326 5.007 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:41:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:41:38_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:41:38_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:41:38_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:41:38_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
1:14.762
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.317
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.444
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with roleName='password text'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700: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: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
After features/support/hooks.rb:326 5.093 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:45:35)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:45:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:45:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:45:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/01:45:35_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Feature: Packages are up-to-date
Tags: @source
14.359
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 14.359
Command 
Command failed (returned pid 77461 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/tmp/tails-amd64-20634-greeter-tps-update-failure-fix@f89ed2ae99+stable@d78e968536-20241105T0640Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/tmp/tails-amd64-20634-greeter-tps-update-failure-fix@f89ed2ae99+stable@d78e968536-20241105T0640Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20240909-1) to Debian trixie (20240909-2)
.
<0> expected but was
<#<Process::Status: pid 77461 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20634-greeter-tps-update-failure-fix/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: Tails persistence
Tags: @product
55.851
Scenario Manual filesystem repair is successful
Before features/support/hooks.rb:269 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 9.386
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 5.617
When I try to enable persistence 0.404
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 6.102
When I repair the filesystem of the Persistent Storage 1.296
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.287
And the filesystem of the Persistent Storage was repaired 0.080
When I close the filesystem repair dialog 1.318
Then persistence is successfully enabled 31.359
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:693:in `block (2 levels) in <top (required)>'
./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/usb.rb:691: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/usb.rb:691:in `/^persistence is successfully enabled$/'
features/persistence.feature:181:in `Then persistence is successfully enabled'
After features/support/hooks.rb:326 5.092 
SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 03:34:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/03:34:33_Manual_filesystem_repair_is_successful.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/03:34:33_Manual_filesystem_repair_is_successful.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/03:34:33_Manual_filesystem_repair_is_successful.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/03:34:33_Manual_filesystem_repair_is_successful.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
46.949
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.389
Then the amnesiac Videos directory exists 0.060
And there is a GNOME bookmark for the amnesiac Videos directory 1.792
Then I start the Tor Browser in offline mode 22.423
And I can save the current page as "index.html" to the Videos GNOME bookmark 14.283
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: AttributeError: 'NoneType' object has no attribute 'querySelection'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:205:in `get_field'
./features/support/helpers/dogtail.rb:233:in `selected?'
./features/step_definitions/browser.rb:560:in `block (2 levels) in <top (required)>'
./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/browser.rb:558: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/browser.rb:558:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:146:in `And I can save the current page as "index.html" to the Videos GNOME bookmark'
features/torified_browsing.feature:139:in `And I can save the current page as "index.html" to the <dir> GNOME bookmark'
After features/support/hooks.rb:326 5.512 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#5)' (at time 04:16:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/04:16:57_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/04:16:57_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/04:16:57_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/12/artifact/build-artifacts/04:16:57_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___5_.journal
After features/support/hooks.rb:100 0.000