Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 72 18 Dec 2024, 07:30

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
22:53.245
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.849
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.061
And Tor is ready 22.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.635
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.691
Given I shutdown Tails and wait for the computer to power off 10.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:50.507
execution 
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/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 10.797 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:06:08)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:06:08_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.008
Feature: Emergency shutdown
Tags: @product @not_release_blocker
2:21.411
Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.209
And I prepare Tails for memory erasure tests 0.460
And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 37.753
And I fill the USB drive with a known pattern 1.314
And I read the content of the test FS 0.060
And patterns cover at least 99% of the test FS size in the guest's memory 2.669 
Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)
When I eject the boot medium 0.822
And I wait for Tails to finish wiping the memory 1:30.120
cannot 
cannot find MemoryWipeCompleted.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/erase_memory.rb:232:in `/^I wait for Tails to finish wiping the memory$/'
features/emergency_shutdown.feature:44:in `And I wait for Tails to finish wiping the memory'
Then I find very few patterns in the guest's memory 0.000
After features/support/hooks.rb:326 10.597 
SCENARIO FAILED: 'Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4' (at time 02:11:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:11:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:11:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/02:11:39_Tails_erases_memory_on_DVD_boot_medium_removal:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.001
Feature: Tails persistence
Tags: @product @doc
1:14.733
Scenario Filesystem and I/O errors
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 8.632
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 4.748
And Tails detects disk read failures on the boot device 0.444
When I try to enable persistence 0.542
Then the Welcome Screen tells me that my hardware is probably failing 4.375
When I log in to a new session 21.569
And all notifications have disappeared 7.868
Then the Tor Browser starts 26.552
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/browser.rb:465:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 7.213 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 03:51:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/03:51:23_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/03:51:23_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/03:51:23_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/03:51:23_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:37.028
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.137
And the network is plugged 0.100
And I successfully configure Tor 22.286
And available upgrades have been checked 0.058
And all notifications have disappeared 4.191
Then the persistent Tor Browser directory exists 0.050
And there is a GNOME bookmark for the persistent Tor Browser directory 1.820
When I start the Tor Browser 22.087
And I open the address "https://tails.net/about" in the Tor Browser 15.000
And "Tails - How Tails works" has loaded in the Tor Browser 1.243
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 15.051
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: Error: atspi_error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (1)
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:358:in `block in grabFocus'
./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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554: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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark'
And I open the address "file:///home/amnesia/Persistent/Tor Browser/index.html" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the persistent Tor Browser directory 0.000
After features/support/hooks.rb:326 7.344 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:27:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:27:32_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:27:32_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:27:32_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:27:32_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
52.380
Scenario Outline The default XDG directories are usable in Tor Browser
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.613
Then the amnesiac Documents directory exists 0.089
And there is a GNOME bookmark for the amnesiac Documents directory 1.594
Then I start the Tor Browser in offline mode 26.788
And I can save the current page as "index.html" to the Documents GNOME bookmark 15.294
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:142:in `And I can save the current page as "index.html" to the Documents 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 6.126 
SCENARIO FAILED: 'The default XDG directories are usable in Tor Browser, Examples (#1)' (at time 04:28:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:28:31_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:28:31_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:28:31_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/72/artifact/build-artifacts/04:28:31_The_default_XDG_directories_are_usable_in_Tor_Browser,_Examples___1_.journal
After features/support/hooks.rb:100 0.000