Project Number Date
test_Tails_ISO_stable 4678 22 Feb 2024, 12:15

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product
3:52.498
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.006
Steps
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 3:52.313
cannot 
cannot find GnomeApplicationsMenu.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:546:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:501: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/step_definitions/common_steps.rb:286: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:291 3.966 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:38:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:38:21_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:38:21_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:38:21_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:38:21_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
57.471
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:245 0.004
Steps
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.293
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:327:in `initialize'
./features/support/helpers/dogtail.rb:256:in `new'
./features/support/helpers/dogtail.rb:256:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:264:in `child'
./features/step_definitions/usb.rb:653:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:665:in `/^I enable persistence( with the changed passphrase)?$/'
./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: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:291 4.047 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:39:23)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:39:23_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_stable/4678/artifact/build-artifacts/01:39:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:39:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:39:23_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:75 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
1:0.818
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:245 0.005
Steps
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.622
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:327:in `initialize'
./features/support/helpers/dogtail.rb:256:in `new'
./features/support/helpers/dogtail.rb:256:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:264:in `child'
./features/step_definitions/usb.rb:653:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:665:in `/^I enable persistence( with the changed passphrase)?$/'
./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
After features/support/hooks.rb:291 4.051 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:43:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:43:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:43:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:43:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/01:43:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:75 0.015
Feature: Localization
Tags: @product
3:36.634
Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)
Before features/support/hooks.rb:245 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 18.497
And I log in to a new session in German (de) 3:18.137
cannot 
cannot find GnomeApplicationsMenuGerman.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:546:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:501: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/localization.feature:15:in `And I log in to a new session in German (de)'
features/localization.feature:9:in `And I log in to a new session in German (de)'
Then the amnesiac Downloads directory exists 0.000
And there is a GNOME bookmark for the amnesiac Downloads directory 0.000
After features/support/hooks.rb:291 4.114 
SCENARIO FAILED: 'Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255), Examples (#2)' (at time 02:13:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/02:13:08_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/02:13:08_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/02:13:08_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4678/artifact/build-artifacts/02:13:08_Do_not_localize_the_XDG_User_Dirs_to_be_able_to_use_those_dirs_in_Tor_Browser___19255_,_Examples___2_.journal
After features/support/hooks.rb:75 0.000
Feature: Packages are up-to-date
Tags: @source
2.685
Scenario All packages are up-to-date
Before features/support/hooks.rb:467 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 2.684
Command 
Command failed (returned pid 63844 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@5869c166d6-20240222T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@5869c166d6-20240222T0716Z.build-manifest

INFO: Need to upgrade to a new APT snapshot:

  - cryptsetup (2:2.6.1-4~deb11u1~tails1) to Debian bookworm (2:2.6.1-4~deb12u2)

  - libdatetime-timezone-perl (1:2.47-1+2023c) to Debian bullseye (1:2.47-1+2024a)
.
<0> expected but was
<#<Process::Status: pid 63844 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:474 0.000
After features/support/hooks.rb:75 0.000