Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 25 16 Aug 2024, 18:40

Failures Overview

The following summary displays scenarios that failed.

Feature: Untrusted partitions
Tags: @product
4:15.079
Scenario Booting Tails does not automount untrusted partitions
Before features/support/hooks.rb:269 0.001
Steps
Given a computer 0.164
And I temporarily create a 100 MiB disk named "gpt_ext2" 0.038
And I create a gpt partition with an ext2 filesystem on disk "gpt_ext2" 6.150
And I plug SATA drive "gpt_ext2" 1.053
And I temporarily create a 100 MiB disk named "msdos_fat32" 0.047
And I create an msdos partition with a vfat filesystem on disk "msdos_fat32" 6.151
And I plug SATA drive "msdos_fat32" 1.074
And I start Tails from DVD with network unplugged and I login 4:0.399
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:562:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:518: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:273:in `/^I start Tails( from DVD)?( with network unplugged)?( and I login)?$/'
features/untrusted_partitions.feature:48:in `And I start Tails from DVD with network unplugged and I login'
Then drive "gpt_ext2" is detected by Tails 0.000
And drive "gpt_ext2" is not mounted 0.000
And drive "msdos_fat32" is detected by Tails 0.000
And drive "msdos_fat32" is not mounted 0.000
After features/support/hooks.rb:326 4.959 
SCENARIO FAILED: 'Booting Tails does not automount untrusted partitions' (at time 00:09:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/00:09:42_Booting_Tails_does_not_automount_untrusted_partitions.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/00:09:42_Booting_Tails_does_not_automount_untrusted_partitions.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/00:09:42_Booting_Tails_does_not_automount_untrusted_partitions.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/00:09:42_Booting_Tails_does_not_automount_untrusted_partitions.journal
After features/support/hooks.rb:100 0.006
Feature: Packages are up-to-date
Tags: @source
0.192
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 0.192
Command 
Command failed (returned pid 55739 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/tmp/tails-amd64-15451-support-manual-fsck-on-error@7641c17fc2+stable@c7db60a915-20240816T1311Z.build-manifest", {:err=>[:child, :out]}]:
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 417, in <module>
    main()
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 386, in main
    suites = tuple(get_suites(config.get("distribution")))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/bin/needed-package-updates", line 334, in get_suites
    codename_pos = ddi_s.index(min_codename)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: 'bullseye' is not in list
.
<0> expected but was
<#<Process::Status: pid 55739 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_15451-support-manual-fsck-on-error/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
1:16.202
Scenario Manual filesystem repair
Before features/support/hooks.rb:269 0.006
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.465
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.353
When I try to enable persistence 0.382
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 1:0.001
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:1733:in `/^the Welcome Screen tells me that filesystem errors were found on the Persistent Storage$/'
features/persistence.feature:175:in `Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage'
When I repair the filesystem of the Persistent Storage 0.000
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.000
And the filesystem of the Persistent Storage was repaired 0.000
When I close the filesystem repair dialog 0.000
Then persistence is successfully enabled 0.000
After features/support/hooks.rb:326 10.616 
SCENARIO FAILED: 'Manual filesystem repair' (at time 03:36:33)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/03:36:33_Manual_filesystem_repair.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/03:36:33_Manual_filesystem_repair.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/25/artifact/build-artifacts/03:36:33_Manual_filesystem_repair.journal
After features/support/hooks.rb:100 0.000