Project Number Date
test_Tails_ISO_devel 3405 29 May 2024, 17:33

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:4.433
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:259 0.008
Before features/support/hooks.rb:456 0.009
Steps
Given a computer 0.197
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:22.223
And I configure APT to prefer an old version of cowsay 0.033
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.439
And I accept adding "cowsay" to Additional Software 6.271
And Additional Software is correctly configured for package "cowsay" 0.876
And I shutdown Tails and wait for the computer to power off 6.377
And I start Tails from USB drive "__internal" with network unplugged 58.773
And I enable persistence 8.784
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.024
And I log in to a new session 38.368
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 41.065
And I revert the APT tweaks that made it prefer an old version of cowsay 0.055
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.073
And the network is plugged 0.041
And Tor is ready 20.968
# Note: the next step races against the appearance of the "The
# upgrade of your additional software failed" notification.
# It should win most of the time, which is good, but there's no
# guarantee it does. If it loses, then it'll remove the notification
# we'll be trying to interact with below ("I can open…")
And all notifications have disappeared 41.494
And available upgrades have been checked 0.738
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.180
And I can open the Additional Software configuration window from the notification 30.446
The 
The Dogtail init script raised: SearchError: descendent of [application | gnome-shell]: child with name="Configure" roleName='push button'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:335:in `initialize'
./features/support/helpers/dogtail.rb:264:in `new'
./features/support/helpers/dogtail.rb:264:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:272:in `child'
./features/step_definitions/additional_software_packages.rb:41:in `click_gnome_shell_notification_button'
./features/step_definitions/additional_software_packages.rb:164:in `/^I can open the Additional Software configuration window from the notification$/'
features/additional_software_packages.feature:106:in `And I can open the Additional Software configuration window from the notification'
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:464 0.033
After features/support/hooks.rb:305 4.872 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:31:25)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/01:31:25_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:89 0.053
Feature: Upgrading an old Tails USB installation
Tags: @product
22:5.936
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:259 0.005
Steps
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:5.765
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:295: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:305 9.903 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:00:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:00:21_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:00:21_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
After features/support/hooks.rb:89 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
2:14.209
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.007
Steps
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.588
Then all tps features from the old Tails version are active 1.519
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.570
And the expected persistent files created with the old Tails version are present in the filesystem 0.047
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:22:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1045:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1044:in `each'
./features/step_definitions/usb.rb:1044:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:305 4.307 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:05:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3405/artifact/build-artifacts/02:05:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:89 0.009