Project Number Date
test_Tails_ISO_devel 3583 10 Nov 2024, 13:00

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
24:5.132
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 13.197
And no SquashFS delta is installed 0.296
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.487
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.077
And Tor is ready 51.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.654
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22:58.478
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderDownloadComplete.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1320:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:91:in `And I can successfully install the incremental upgrade to version 6.2~testoverlayfs'
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.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 5.752 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:14:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
39.212
Scenario I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.840
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.153
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.047
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.062
And the file "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.063
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.150
When I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 3.698
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 2.851
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.088
When I close Evince 0.199
Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.137
When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 2.155
Then Evince tells me it cannot open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.551
And AppArmor has denied "/usr/bin/evince" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.077
When I close Evince 20.132
Process 
Process 'evince' is still running after waiting for 20 seconds (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/common_steps.rb:823:in `/^process "([^"]+)" has stopped running after at most (\d+) seconds$/'
./features/step_definitions/evince.rb:34:in `/^I close Evince$/'
features/evince.feature:36:in `When I close Evince'
Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.000
When I try to open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /usr/lib/live/mount/overlay.
And AppArmor has denied "/usr/bin/evince" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:326 4.936 
SCENARIO FAILED: 'I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg' (at time 02:28:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:28:31_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:28:31_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:28:31_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/02:28:31_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
55.813
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:269 0.007
Before features/support/hooks.rb:507 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.278
And the network is plugged 0.104
And Tor is ready 19.916
And available upgrades have been checked 0.060
And all notifications have disappeared 4.194
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 12.003
Then I see Pidgin's account manager window 4.234
When I create my XMPP account 4.020
cannot 
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:149:in `find'
./features/support/helpers/screen.rb:333:in `hover'
./features/support/helpers/screen.rb:360:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:68:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:515 0.031
After features/support/hooks.rb:326 5.178 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 04:12:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/04:12:26_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/04:12:26_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/04:12:26_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3583/artifact/build-artifacts/04:12:26_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:100 0.000