Cucumber Reports (no 4832) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	4832	08 May 2024, 12:47

Feature: System memory erasure on shutdown

21.487

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:259 0.003

Steps

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

And I prepare Tails for memory erasure tests 0.448

When I start a process allocating 128 MiB of memory with a known pattern 2.321

Then patterns cover at least 128 MiB in the guest's memory 4.544

Output 1

Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.265

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

6.480%

6.480% of the free memory still has the pattern, but less than 0.800% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:219:in `/^I find very few patterns in the guest's memory$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory'

Output 1

Pattern coverage: 6.480% (56 MiB out of 871 MiB reference memory)

Hooks

After features/support/hooks.rb:305 6.433

Output 1

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:29:09)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/00:29:09_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/00:29:09_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/00:29:09_Erasure_of_memory_freed_by_killed_userspace_processes.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/00:29:09_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:89 0.000

Feature: Additional software

Tags: @product @check_tor_leaks @slow

26:52.822

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.011

Steps

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

And I update APT using apt 18.436

And I install "popularity-contest" using apt 25.727

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

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

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

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

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

And I enable persistence 26.510

And I log in to a new session 35.622

And the Additional Software installation service has started 2:23.627

Then I am notified that the installation succeeded 20:0.117

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:587:in `new'
./features/step_definitions/common_steps.rb:587:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'

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.048

After features/support/hooks.rb:305 9.845

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:34:15)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/01:34:15_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/4832/artifact/build-artifacts/01:34:15_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

After features/support/hooks.rb:89 0.011

Feature: Upgrading an old Tails USB installation

Tags: @product

2:15.104

Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled

Hooks

Before features/support/hooks.rb:259 0.008

Steps

Given a computer 0.307

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

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/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'

Then all tps features from the old Tails version are active 0.000

And Tails is running from USB drive "to_upgrade" 0.000

And the boot device has safe access rights 0.000

And the expected persistent files created with the old Tails version are present in the filesystem 0.000

And all persistent directories from the old Tails version have safe access rights 0.000

Hooks

After features/support/hooks.rb:305 4.489

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:09:28)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:09:28_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:09:28_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:09:28_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_stable/4832/artifact/build-artifacts/02:09:28_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:89 0.011

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

4:57.899

Scenario Upgrading an initial Tails installation with an incremental upgrade

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 17.574

And no SquashFS delta is installed 0.155

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

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

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

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

When the network is plugged 0.048

And Tor is ready 20.563

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

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

Given I shutdown Tails and wait for the computer to power off 1:33.624

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

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/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

Hooks

After features/support/hooks.rb:305 4.434

Output 1

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:31)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/02:14:31_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:89 0.009

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

Tags: @product

23.255

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.668

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

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.267

Output 1

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

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

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

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

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

After features/support/hooks.rb:89 0.000

Feature: Tails persistence

Tags: @product

2:54.204

Scenario Creating and using a persistent NetworkManager connection

Hooks

Before features/support/hooks.rb:259 0.005

Steps

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

And the network is plugged 0.053

And Tor is ready 18.956

And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.345

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

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

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:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

And I capture all network traffic 0.000

And the network is plugged 0.000

And Tor is ready 0.000

And I switch to the "persistent-con-current" NetworkManager connection 0.000

And the 1st network device has a spoofed MAC address configured 0.000

And no network device leaked the real MAC address 0.000

Hooks

After features/support/hooks.rb:305 4.319

Output 1

SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 03:35:11)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:35:11_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:35:11_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:35:11_Creating_and_using_a_persistent_NetworkManager_connection.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:35:11_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:89 0.011

Feature: Tails persistence

Tags: @product

3:15.477

Scenario Changing the Persistent Storage passphrase

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 10.512

# Note that if anything fails after the passphrase was changed and

# before it's changed back below, subsequent scenarios might fail

# because the Persistent Storage doesn't have the expected passphrase.

When I change the passphrase of the Persistent Storage 40.328

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

Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 2:9.082

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:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'

And I change the passphrase of the Persistent Storage back to the original 0.000

Hooks

After features/support/hooks.rb:305 4.152

Output 1

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:44:54)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:44:54_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:44:54_Changing_the_Persistent_Storage_passphrase.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:44:54_Changing_the_Persistent_Storage_passphrase.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:44:54_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:89 0.025

Feature: Tails persistence

Tags: @product

1:38.993

Scenario Feature activation fails

Hooks

Before features/support/hooks.rb:259 0.004

Steps

Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.702

And I create a symlink "/home/amnesia/Persistent" to "/etc" 0.098

When I try to enable persistence 0.309

Then the Welcome Screen tells me that the Persistent Folder feature couldn't be activated 34.294

When I log in to a new session after having activated the Persistent Storage 43.663

And all notifications have disappeared 10.926

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/persistence.feature:148:in `And all notifications have disappeared'

Then the Persistent Storage settings tell me that the Persistent Folder feature couldn't be activated 0.000

And all tps features are enabled 0.000

And all tps features but the first one are active 0.000

Hooks

After features/support/hooks.rb:305 4.712

Output 1

SCENARIO FAILED: 'Feature activation fails' (at time 03:50:12)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:50:12_Feature_activation_fails.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:50:12_Feature_activation_fails.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:50:12_Feature_activation_fails.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4832/artifact/build-artifacts/03:50:12_Feature_activation_fails.journal

After features/support/hooks.rb:89 0.000