Cucumber Reports (no 4818) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4818	30 Apr 2024, 19:00

Feature: System memory erasure on shutdown

7:0.597

Scenario Erasure of read and write disk caches of persistent data on shutdown

Hooks

Before features/support/hooks.rb:259 0.002

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7:0.597

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:152:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:149:in `each'
./features/step_definitions/snapshots.rb:149:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:172:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:76: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

And I wait 20 seconds 0.000

Then I find very few patterns in the guest's memory 0.000

Hooks

After features/support/hooks.rb:305 4.213

Output 1

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/00:39:19_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/00:39:19_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/00:39:19_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/00:39:19_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:89 0.015

Feature: Additional software

Tags: @product @check_tor_leaks @slow

7:0.199

Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails

Hooks

Before features/support/hooks.rb:259 0.003

Before features/support/hooks.rb:456 0.004

Steps

Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:0.585

And I update APT using apt 18.853

And I install "popularity-contest" using apt 25.881

Then I am proposed to add the "popularity-contest" package to my Additional Software 6.761

When I create a persistent storage and activate the Additional Software feature 22.513

Then Additional Software is correctly configured for package "popularity-contest" 1.422

When I shutdown Tails and wait for the computer to power off 12.857

And I start Tails from USB drive "__internal" with network unplugged 1:0.505

And I enable persistence 26.873

And I log in to a new session 3:3.944

cannot

cannot find GnomeApplicationsMenu.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/common_steps.rb:558:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:514:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/additional_software_packages.feature:37:in `And I log in to a new session'

And the Additional Software installation service has started 0.000

Then I am notified that the installation succeeded 0.000

And Additional Software is correctly configured for package "popularity-contest" 0.000

And the package "popularity-contest" is installed after Additional Software has been started 0.000

Hooks

After features/support/hooks.rb:464 0.045

After features/support/hooks.rb:305 5.550

Output 1

SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:20:05)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.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_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:20:05_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal

After features/support/hooks.rb:89 0.012

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

7:5.102

Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online

Hooks

Before features/support/hooks.rb:259 0.004

Before features/support/hooks.rb:456 0.005

Steps

Given a computer 0.209

And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:33.598

And I configure APT to prefer an old version of cowsay 0.027

When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.826

And I accept adding "cowsay" to Additional Software 6.916

And Additional Software is correctly configured for package "cowsay" 0.876

And I shutdown Tails and wait for the computer to power off 6.168

And I start Tails from USB drive "__internal" with network unplugged 1:0.800

And I enable persistence 13.918

# 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.023

And I log in to a new session 31.283

And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 31.742

And I revert the APT tweaks that made it prefer an old version of cowsay 0.051

# 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.069

And the network is plugged 0.086

And Tor is ready 20.328

# 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 39.679

And available upgrades have been checked 0.513

And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 1.181

And I can open the Additional Software configuration window from the notification 30.801

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

Hooks

After features/support/hooks.rb:464 0.041

After features/support/hooks.rb:305 5.177

Output 1

SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:35:45)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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_stable/4818/artifact/build-artifacts/01:35:45_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.021

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

2:8.264

Scenario I am notified when Additional Software fails to install a package

Hooks

Before features/support/hooks.rb:259 0.006

Before features/support/hooks.rb:456 0.009

Steps

Given a computer 0.221

And I start Tails from USB drive "__internal" with network unplugged 1:1.436

And I enable persistence 13.174

And I remove the "cowsay" deb files from the APT cache 0.749

# Prevent the "Warning: virtual machine detected!" notification from racing

# with the one we'll be interacting with below.

And I disable the tails-virt-notify-user.service user unit 0.102

And I log in to a new session 41.348

Then I see the "The installation of your additional software failed" notification after at most 300 seconds 11.231

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:587:in `new'
./features/step_definitions/common_steps.rb:587:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:132:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'

And I can open the Additional Software log file from the notification 0.000

And the package "cowsay" is not installed 0.000

Hooks

After features/support/hooks.rb:464 0.039

After features/support/hooks.rb:305 4.735

Output 1

SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:37:59)

Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.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_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:37:59_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:89 0.010

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

8:8.034

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

Before features/support/hooks.rb:259 0.006

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.040

And no SquashFS delta is installed 0.282

And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323

And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057

And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300

And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424

When the network is plugged 0.051

And Tor is ready 21.553

Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.496

And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.334

Given I shutdown Tails and wait for the computer to power off 10.645

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.086

Then Tails is running version 6.2~testoverlayfs 0.017

And all tps features are active 2.499

And the file system changes introduced in version 6.2~testoverlayfs are present 0.395

And only the 6.2~testoverlayfs SquashFS delta is installed 0.071

# Our IUK sets a release date that can make Tor bootstrapping impossible

Given Tails system time is magically synchronized 0.401

# 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.255

When the network is plugged 0.035

And Tor is ready 16.692

Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.620

And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.944

Given I shutdown Tails and wait for the computer to power off 4.237

When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 4:20.267

cannot

cannot find GnomeApplicationsMenu.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/common_steps.rb:558:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:514:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/common_steps.rb:292: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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

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

Hooks

After features/support/hooks.rb:305 4.669

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:58:54)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/01:58:54_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:89 0.017

Feature: Tails-related cryptographic keys are up-to-date

Tags: @product

23.781

Scenario The included APT repository keys are up-to-date

Hooks

Before features/support/hooks.rb:259 0.007

Steps

Given I have started Tails from DVD without network and logged in 9.518

Then the keys trusted by APT are valid for the next 3 months 14.262

The

The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'

Hooks

After features/support/hooks.rb:305 4.474

Output 1

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:23:38)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/02:23:38_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/02:23:38_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/02:23:38_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/02:23:38_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000

Feature: Tails persistence

Tags: @product

2:34.828

Scenario Dotfiles persistence

Hooks

Before features/support/hooks.rb:259 0.008

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.891

When I write some dotfile expected to persist 0.056

And I shutdown Tails and wait for the computer to power off 8.816

And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.064

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711: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/persistence.feature:139:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

Then the expected persistent dotfile is present in the filesystem 0.000

Hooks

After features/support/hooks.rb:305 4.210

Output 1

SCENARIO FAILED: 'Dotfiles persistence' (at time 03:33:44)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/03:33:44_Dotfiles_persistence.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/03:33:44_Dotfiles_persistence.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/03:33:44_Dotfiles_persistence.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/03:33:44_Dotfiles_persistence.journal

After features/support/hooks.rb:89 0.007

Feature: Browsing the web using the Tor Browser

Tags: @product

3:20.577

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:259 0.007

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.938

And all tps features are active 2.305

And all persistent filesystems have safe access rights 0.227

And all persistence configuration files have safe access rights 0.416

And all persistent directories have safe access rights 2.579

When I start the Tor Browser in offline mode 23.163

And I add a bookmark to eff.org in the Tor Browser 19.387

And I cold reboot the computer 12.748

And the computer reboots Tails 1:0.922

And I enable persistence 18.302

And I log in to a new session 38.518

And all notifications have disappeared 11.067

The

The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711: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

Hooks

After features/support/hooks.rb:305 4.409

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 04:22:36)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/04:22:36_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/04:22:36_Persistent_browser_bookmarks.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/04:22:36_Persistent_browser_bookmarks.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4818/artifact/build-artifacts/04:22:36_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:89 0.010