Project Number Date
test_Tails_ISO_20634-greeter-tps-update-failure-fix 16 11 Nov 2024, 12:41

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
1:41.467
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:269 0.007
Steps
Given a computer 1.473
And I start the computer from DVD with network unplugged 38.205
When Tails detects disk read failures on the SquashFS 1.404
Then I see a disk failure message on the splash screen 1:0.384
cannot find PlymouthDiskFailureMessage.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/hardware.rb:62:in `/^I see a disk failure message on the splash screen$/'
features/hardware_failure.feature:14:in `Then I see a disk failure message on the splash screen'
features/hardware_failure.feature:11:in `Then I see a disk failure message on the splash screen'
After features/support/hooks.rb:326 4.930

SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#1)' (at time 02:13:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/02:13:26_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/02:13:26_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/02:13:26_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/02:13:26_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.journal

After features/support/hooks.rb:100 0.008
Tags: @source
13.265
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 13.265
Command failed (returned pid 57712 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@874cbb48b2-20241111T0639Z.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@874cbb48b2-20241111T0639Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - base-files (12.4+deb12u7) to Debian bookworm (12.4+deb12u8)
  - cjson (1.7.15-1+deb12u1) to Debian bookworm (1.7.15-1+deb12u2)
  - curl[curl] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - curl[libcurl3-gnutls, libcurl4] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - distro-info-data (0.58+deb12u2) to Debian bookworm (0.58+deb12u3)
  - glib2.0 (2.74.6-2+deb12u3) to Debian bookworm (2.74.6-2+deb12u4)
  - glibc[libc-dev-bin, libc6-dev, libc-l10n, libc6, libc-bin] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - glibc[locales] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - gtk+3.0[gtk-update-icon-cache, gir1.2-gtk-3.0] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - gtk+3.0[libgtk-3-bin, libgtk-3-0, libgtk-3-common] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - intel-microcode (3.20240813.1~deb12u1) to Debian bookworm (3.20240910.1~deb12u1)
  - iputils (3:20221126-1) to Debian bookworm (3:20221126-1+deb12u1)
  - ntfs-3g[libntfs-3g89] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - ntfs-3g[ntfs-3g] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - python-cryptography (38.0.4-3) to Debian bookworm (38.0.4-3+deb12u1)
  - sqlite3 (3.40.1-2) to Debian bookworm (3.40.1-2+deb12u1)
  - systemd[libnss-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libpam-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libsystemd0, libsystemd-shared, libudev1, libudev-dev] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[systemd, systemd-sysv, systemd-timesyncd, systemd-oomd, udev] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
.
<0> expected but was
<#<Process::Status: pid 57712 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
Tags: @product
22:39.138
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.704
Then Tails is running from USB drive "__internal" 0.364
And all tps features are active 2.793
And all persistent directories have safe access rights 2.745
When I disable the first tps feature 5.986
Then all tps features but the first one are active 2.303
And I shutdown Tails and wait for the computer to power off 8.796
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:5.443
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/step_definitions/common_steps.rb:298: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/persistence.feature:49:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:326 10.820

SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:30:19)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:30:19_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:30:19_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:30:19_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal

After features/support/hooks.rb:100 0.009
Tags: @product
57.597
Scenario Manual filesystem repair is successful
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.816
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.318
When I try to enable persistence 0.430
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 6.848
When I repair the filesystem of the Persistent Storage 1.255
Then the Welcome Screen tells me that the filesystem was repaired successfully 0.271
And the filesystem of the Persistent Storage was repaired 0.091
When I close the filesystem repair dialog 1.225
Then persistence is successfully enabled 31.339
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.589

SCENARIO FAILED: 'Manual filesystem repair is successful' (at time 03:59:50)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:59:50_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/16/artifact/build-artifacts/03:59:50_Manual_filesystem_repair_is_successful.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:59:50_Manual_filesystem_repair_is_successful.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/03:59:50_Manual_filesystem_repair_is_successful.journal

After features/support/hooks.rb:100 0.000
Tags: @product
23:5.209
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:269 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.173
And all tps features are active 2.531
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.468
And all persistent directories have safe access rights 2.875
When I start the Tor Browser in offline mode 23.664
And I add a bookmark to eff.org in the Tor Browser 11.860
And I cold reboot the computer 11.792
And the computer reboots Tails 1:0.964
And I enable persistence 17.875
And I log in to a new session 42.618
And all notifications have disappeared 20:0.127
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.874

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 05:08:00)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/05:08:00_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/05:08:00_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-update-failure-fix/16/artifact/build-artifacts/05:08:00_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.013