Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 10 29 Oct 2024, 18:48

Failures Overview

The following summary displays scenarios that failed.

5:58.443
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5:58.443
The
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:

 (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:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:326 5.104

SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 00:39:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/00:39:26_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/00:39:26_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/00:39:26_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/00:39:26_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:100 0.009
Tags: @product
2:14.438
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 12.590
And I enable persistence but something goes wrong during the LUKS header upgrade 2:1.848
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:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:712:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:326 5.778

SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:51:51)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/03:51:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/03:51:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/03:51:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/03:51:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal

After features/support/hooks.rb:100 0.000
3:35.157
Scenario The Tor Browser directory is usable
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.011
Then the amnesiac Tor Browser directory exists 0.054
And there is a GNOME bookmark for the amnesiac Tor Browser directory 2.028
And the persistent Tor Browser directory does not exist 0.079
When I start the Tor Browser 19.874
And the Tor Browser loads the startup page 3:0.109
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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:24:in `And the Tor Browser loads the startup page'
Then I can save the current page as "index.html" to the default downloads directory 0.000
And I can print the current page as "output.pdf" to the default downloads directory 0.000
After features/support/hooks.rb:515 0.029
After features/support/hooks.rb:326 5.857

SCENARIO FAILED: 'The Tor Browser directory is usable' (at time 04:29:30)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:29:30_The_Tor_Browser_directory_is_usable.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:29:30_The_Tor_Browser_directory_is_usable.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:29:30_The_Tor_Browser_directory_is_usable.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:29:30_The_Tor_Browser_directory_is_usable.journal

After features/support/hooks.rb:100 0.000
Tags: @product
3:33.460
Scenario I can view a file stored in "~/Tor Browser" but not in ~/.gnupg
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.986
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Tor Browser/synaptic.html" as user "amnesia" 0.113
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.059
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.055
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.066
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.060
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.067
And the file "/tmp/synaptic.html" exists 0.064
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.166
When I start the Tor Browser 19.731
And the Tor Browser loads the startup page 3:0.087
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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:61:in `And the Tor Browser loads the startup page'
And I open the address "file:///home/amnesia/Tor Browser/synaptic.html" in the Tor Browser 0.000
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Tor Browser/synaptic.html" 0.000
Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.000
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
And AppArmor has denied "torbrowser_firefox" from opening "/home/amnesia/.gnupg/synaptic.html" 0.000
Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.000
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
And AppArmor has denied "torbrowser_firefox" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" 0.000
Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.000
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /lib/live/mount/overlay.
And AppArmor has denied "torbrowser_firefox" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" 0.000
# We do not get any AppArmor log for when access to files in /tmp is denied
# since we explictly override (commit 51c0060) the rules (from the user-tmp
# abstraction) that would otherwise allow it, and we do so with "deny", which
# also specifies "noaudit". We could explicitly specify "audit deny" and
# then have logs, but it could be a problem when we set up desktop
# notifications for AppArmor denials (#9337).
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 0.000
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.000
After features/support/hooks.rb:326 7.481

SCENARIO FAILED: 'I can view a file stored in "~/Tor Browser" but not in ~/.gnupg' (at time 04:37:00)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:37:00_I_can_view_a_file_stored_in____Tor_Browser__but_not_in___.gnupg.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:37:00_I_can_view_a_file_stored_in____Tor_Browser__but_not_in___.gnupg.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:37:00_I_can_view_a_file_stored_in____Tor_Browser__but_not_in___.gnupg.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/10/artifact/build-artifacts/04:37:00_I_can_view_a_file_stored_in____Tor_Browser__but_not_in___.gnupg.journal

After features/support/hooks.rb:100 0.000