Cucumber Reports (no 3) - Tag: @product

Project	Number	Date
test_Tails_ISO_15451-support-manual-fsck-on-error	3	24 Jul 2024, 19:22

	Steps	Scenarios	Features
@product	1161	38	323	0	0	1522	166	40	206	4:23:48.898	Failed

Feature: Untrusted partitions

Tags: @product

2:15.578

Scenario Tails ignores a swap volume and another Tails that are on an internal hard drive

Hooks

Before features/support/hooks.rb:269 0.035

Steps

Given a computer 0.592

And I temporarily create a 100 MiB disk named "swap" 0.133

And I create a gpt swap partition on disk "swap" 12.135

And I plug SATA drive "swap" 1.062

And I temporarily create a 2 GiB disk named "live_hd" 0.038

And I write the Tails ISO image to disk "live_hd" 27.376

And I plug SATA drive "live_hd" 1.066

When I start Tails with network unplugged and I login 1:32.708

Then a "swap" partition was detected by Tails on drive "swap" 0.173

And drive "live_hd" is detected by Tails 0.122

But Tails has no disk swap enabled 0.088

And drive "live_hd" is not mounted 0.079

Hooks

After features/support/hooks.rb:326 0.645

After features/support/hooks.rb:100 0.128

Feature: Untrusted partitions

Tags: @product

1:36.019

Scenario The Welcome Screen ignores Persistent Storage stored on a non-removable USB drive

Hooks

Before features/support/hooks.rb:269 0.002

Steps

Given a computer 0.238

And I temporarily create a 100 MiB disk named "fake_TailsData" 0.065

And I create a gpt partition labeled "TailsData" with an ext4 filesystem encrypted with password "asdf" on disk "fake_TailsData" 22.665

And I plug non-removable USB drive "fake_TailsData" 1.068

When I start the computer 1.026

And the computer boots Tails 56.692

Then drive "fake_TailsData" is detected by Tails 0.156

And Tails Greeter has not detected a persistence partition 14.106

Hooks

After features/support/hooks.rb:326 0.850

After features/support/hooks.rb:100 0.007

Feature: Untrusted partitions

Tags: @product

1:35.410

Scenario The Welcome Screen ignores Persistent Storage stored on an internal hard drive

Hooks

Before features/support/hooks.rb:269 0.001

Steps

Given a computer 0.433

And I temporarily create a 100 MiB disk named "fake_TailsData" 0.146

And I create a gpt partition labeled "TailsData" with an ext4 filesystem encrypted with password "asdf" on disk "fake_TailsData" 23.109

And I plug SATA drive "fake_TailsData" 1.063

When I start the computer 1.146

And the computer boots Tails 55.529

Then drive "fake_TailsData" is detected by Tails 0.126

And Tails Greeter has not detected a persistence partition 13.855

Hooks

After features/support/hooks.rb:326 0.789

After features/support/hooks.rb:100 0.009

Feature: Untrusted partitions

Tags: @product

1:35.828

Scenario Booting Tails does not automount untrusted partitions

Hooks

Before features/support/hooks.rb:269 0.002

Steps

Given a computer 0.271

And I temporarily create a 100 MiB disk named "gpt_ext2" 0.063

And I create a gpt partition with an ext2 filesystem on disk "gpt_ext2" 6.491

And I plug SATA drive "gpt_ext2" 1.136

And I temporarily create a 100 MiB disk named "msdos_fat32" 0.078

And I create an msdos partition with a vfat filesystem on disk "msdos_fat32" 6.295

And I plug SATA drive "msdos_fat32" 1.075

And I start Tails from DVD with network unplugged and I login 1:19.979

Then drive "gpt_ext2" is detected by Tails 0.178

And drive "gpt_ext2" is not mounted 0.063

And drive "msdos_fat32" is detected by Tails 0.108

And drive "msdos_fat32" is not mounted 0.086

Hooks

After features/support/hooks.rb:326 1.030

After features/support/hooks.rb:100 0.007

Feature: Root access control enforcement

Tags: @product

2:6.012

Scenario I can perform administrative tasks if I have set up an administration password in the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.002

Steps

Given I have started Tails from DVD without network and logged in with an administration password 2:0.084

And running a command as root with pkexec requires PolicyKit administrator privileges 0.117

Then I can run a command as root with sudo 0.103

Then I can run a command as root with pkexec 5.707

Hooks

After features/support/hooks.rb:326 1.013

After features/support/hooks.rb:100 0.005

Feature: Root access control enforcement

Tags: @product

1:39.597

Scenario If cannot perform administrative tasks unless I have set up an administration password in the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And running a command as root with pkexec requires PolicyKit administrator privileges 0.262

Then I cannot run a command as root with sudo and the standard passwords 0.280

And I cannot run a command as root with pkexec and the standard passwords 18.408

Then I cannot login as root using su with the standard passwords 26.684

Hooks

After features/support/hooks.rb:326 0.894

After features/support/hooks.rb:100 0.000

Feature: Time syncing

Tags: @product @check_tor_leaks

27.223

Scenario Clock with host's time

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

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

When the network is plugged 0.178

And I successfully configure Tor 17.646

Then the system clock is less than 5 minutes incorrect 0.066

Hooks

After features/support/hooks.rb:515 0.606

After features/support/hooks.rb:326 0.902

After features/support/hooks.rb:100 0.000

Feature: Time syncing

Tags: @product @check_tor_leaks

28.885

Scenario Clock with host's time while using bridges

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.003

Steps

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

When the network is plugged 0.042

And the Tor Connection Assistant autostarts 4.208

And I configure some normal bridges in the Tor Connection Assistant 12.010

And I wait until Tor is ready 4.288

Then the system clock is less than 5 minutes incorrect 0.061

Hooks

After features/support/hooks.rb:515 0.547

After features/support/hooks.rb:326 0.733

After features/support/hooks.rb:100 0.000

Feature: Time syncing

Tags: @product @check_tor_leaks

34.601

Scenario Clock is one day in the future while using obfs4 bridges

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

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

When I bump the system time with "+1 day" 0.251

And I capture all network traffic 0.002

And the network is plugged 0.051

And the Tor Connection Assistant autostarts 4.722

And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.412

And I wait until Tor is ready 2.972

Then the system clock is less than 5 minutes incorrect 0.057

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.877

Hooks

After features/support/hooks.rb:515 0.447

After features/support/hooks.rb:326 1.589

After features/support/hooks.rb:100 0.046

Feature: Time syncing

Tags: @product @check_tor_leaks @not_release_blocker

1:26.029

Scenario The system time is not synced to the hardware clock

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.004

Steps

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

When I bump the system time with "-15 days" 0.309

And I warm reboot the computer 0.014

And the computer reboots Tails 1:17.031

Then Tails' hardware clock is close to the host system's time 0.122

Hooks

After features/support/hooks.rb:515 0.168

After features/support/hooks.rb:326 0.782

After features/support/hooks.rb:100 0.006

Feature: Time syncing

Tags: @product @check_tor_leaks @not_release_blocker

1:37.013

Scenario Anti-test: Changes to the hardware clock are kept when rebooting

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.002

Steps

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

When I bump the hardware clock's time with "-15 days" 1.165

And I warm reboot the computer 0.015

And the computer reboots Tails 1:24.217

Then the hardware clock is still off by "-15 days" 0.756

Hooks

After features/support/hooks.rb:515 0.134

After features/support/hooks.rb:326 0.862

After features/support/hooks.rb:100 0.005

Feature: Time syncing

Tags: @product @check_tor_leaks

59.874

Scenario The clock is set to the source date when the hardware clock is way in the past

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.002

Steps

Given a computer 0.165

And the hardware clock is set to "01 Jan 2000 12:34:56" 0.023

And I start the computer 1.054

And the computer boots Tails 58.438

Then the system clock is just past Tails' source date 0.191

Hooks

After features/support/hooks.rb:515 0.130

After features/support/hooks.rb:326 0.715

After features/support/hooks.rb:100 0.006

Feature: Time syncing

Tags: @product @check_tor_leaks

32.752

Scenario On a clock with host's time, Tor Connection works even if time sync fails

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

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

And I make sure time sync before Tor connects times out 1.231

When the network is plugged 0.055

And I successfully configure Tor 23.005

Then the system clock is less than 5 minutes incorrect 0.086

Hooks

After features/support/hooks.rb:515 0.759

After features/support/hooks.rb:326 0.699

After features/support/hooks.rb:100 0.001

Feature: Time syncing

Tags: @product @check_tor_leaks

1:5.018

Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.003

Steps

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

When I bump the system time with "+8 hours +15 minutes" 0.184

And all notifications have disappeared 4.014

And I capture all network traffic 0.002

And I make sure time sync before Tor connects fails 0.140

And the network is plugged 0.063

And the Tor Connection Assistant autostarts 4.655

When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.314

And I click "Connect to Tor" 1.549

And the Tor Connection Assistant fails to connect to Tor 16.672

# The "Fix Clock" button allows users to recover from this bug

Then I set the time zone in Tor Connection to "Asia/Shanghai" 15.229

Then the system clock is less than 20 minutes incorrect 0.260

When I click "Connect to Tor" 1.217

Then I wait until Tor is ready 6.353

And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.756

# check that htpdate has done its job

And the system clock is less than 5 minutes incorrect 0.059

Hooks

After features/support/hooks.rb:515 0.450

After features/support/hooks.rb:326 0.994

After features/support/hooks.rb:100 0.033

Feature: Time syncing

Tags: @product @check_tor_leaks

1:1.142

Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

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

When I bump the system time with "+8 hours +15 minutes" 0.243

And all notifications have disappeared 4.248

And I capture all network traffic 0.002

And the network is plugged 0.057

And the Tor Connection Assistant autostarts 4.103

# Anti-test: Users east of UTC can't connect to obfs4 bridges

And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.595

And I click "Connect to Tor" 1.188

Then the Tor Connection Assistant reports that it failed to connect 11.787

# The "Fix Clock" button allows users to recover from this bug

When I set the time zone in Tor Connection to "Asia/Shanghai" 15.097

Then the system clock is less than 20 minutes incorrect 0.296

# "Asia/Shanghai" is UTC+08:00 all year long (no DST)

And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.466

When I click "Connect to Tor" 1.162

Then I wait until Tor is ready 7.930

And all Internet traffic has only flowed through the configured bridges 1.003

# check that htpdate has done its job

And the system clock is less than 5 minutes incorrect 0.084

And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.433

Hooks

After features/support/hooks.rb:515 0.508

After features/support/hooks.rb:326 0.982

After features/support/hooks.rb:100 0.048

Feature: Time syncing

Tags: @product @check_tor_leaks

25.323

Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check

Hooks

Before features/support/hooks.rb:269 0.002

Before features/support/hooks.rb:507 0.003

Steps

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

And I make sure time sync before Tor connects uses a fake connectivity check service 1.255

And the network is plugged 0.040

And Tor is ready 14.117

Then the fake connectivity check service has received a new HTTP request 0.000

When I make NetworkManager perform a connectivity check 1.601

Then the fake connectivity check service has received a new HTTP request 0.000

And the HTTP requests received by the fake connectivity check service are identical 0.004

Hooks

After features/support/hooks.rb:515 0.667

After features/support/hooks.rb:326 0.692

After features/support/hooks.rb:100 0.000

Feature: Using Tor bridges and pluggable transports

Tags: @product

18.721

Scenario Using normal bridges

Steps

When I configure some normal bridges in the Tor Connection Assistant 13.715

Then I wait until Tor is ready 2.906

And tca.conf includes the configured bridges 0.019

And available upgrades have been checked 1.161

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.918

Hooks

After features/support/hooks.rb:326 0.671

After features/support/hooks.rb:100 0.037

Feature: Using Tor bridges and pluggable transports

Tags: @product

18.878

Scenario Using obfs4 pluggable transports

Steps

When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 13.218

Then I wait until Tor is ready 2.396

And tca.conf includes the configured bridges 0.014

And available upgrades have been checked 2.180

And all Internet traffic has only flowed through the configured bridges 1.068

Hooks

After features/support/hooks.rb:326 1.188

After features/support/hooks.rb:100 0.062

Feature: Using Tor bridges and pluggable transports

Tags: @product

38.263

Scenario Using obfs4 pluggable transports from a QR code

Steps

When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 33.282

Then I wait until Tor is ready 4.040

And tca.conf includes the configured bridges 0.018

And available upgrades have been checked 0.076

And all Internet traffic has only flowed through the configured bridges 0.845

Hooks

After features/support/hooks.rb:326 0.649

After features/support/hooks.rb:100 0.056

Feature: Using Tor bridges and pluggable transports

Tags: @product

1:8.684

Scenario TCA can scan QR code after a connection failure

Steps

Given the Tor network and default bridges are blocked 2.084

When I unsuccessfully configure a direct connection in the Tor Connection Assistant 30.492

Then the Tor Connection Assistant reports that it failed to connect 0.134

And tca.conf is empty 0.217

Given I scan a QR code from the error page in Tor Connection Assistant 22.696

And I retry connecting to Tor 1.178

Then I wait until Tor is ready 10.788

And tca.conf includes the configured bridges 0.012

And available upgrades have been checked 0.060

And all Internet traffic has only flowed through the configured bridges or connectivity check service 1.018

Hooks

After features/support/hooks.rb:326 0.652

After features/support/hooks.rb:100 0.049

Feature: Using Tor bridges and pluggable transports

Tags: @product @supports_real_tor

19.701

Scenario Default Tor bridges

Steps

When I configure the default bridges in the Tor Connection Assistant 14.191

Then I wait until Tor is ready 2.029

And Tor is configured to use the default bridges 1.059

And tca.conf includes no bridge 0.029

And available upgrades have been checked 0.132

And Tor is configured to use the default bridges 1.255

And all Internet traffic has only flowed through the default bridges or connectivity check service 1.004

Hooks

After features/support/hooks.rb:326 1.330

After features/support/hooks.rb:100 0.039

Feature: Using Tor bridges and pluggable transports

Tags: @product

27.850

Scenario Fall back to default bridges if failing to connect directly to the Tor network

Steps

Given the Tor network is blocked 2.283

When I configure a direct connection in the Tor Connection Assistant 21.892

Then I wait until Tor is ready 2.208

And tca.conf includes no bridge 0.013

And available upgrades have been checked 0.048

And Tor is configured to use the default bridges 0.500

And all Internet traffic has only flowed through the default bridges or connectivity check service 0.903

Hooks

After features/support/hooks.rb:326 1.361

After features/support/hooks.rb:100 0.044

Feature: Using Tor bridges and pluggable transports

Tags: @product

53.204

Scenario TCA can reconnect after a connection failure

Steps

Given the Tor network and default bridges are blocked 2.383

When I unsuccessfully configure a direct connection in the Tor Connection Assistant 38.128

Then the Tor Connection Assistant reports that it failed to connect 0.142

And tca.conf is empty 0.248

Given the Tor network and default bridges are unblocked 1.475

And I retry connecting to Tor 1.252

Then I wait until Tor is ready 8.239

And tca.conf includes no bridge 0.020

And available upgrades have been checked 0.074

And all Internet traffic has only flowed through Tor or connectivity check service 1.239

Hooks

After features/support/hooks.rb:326 1.079

After features/support/hooks.rb:100 0.047

Feature: Using Tor bridges and pluggable transports

Tags: @product

5.282

Scenario Normal bridges are not allowed in "Hide" mode

Steps

When I try to configure some normal bridges in the Tor Connection Assistant in hide mode 4.857

Then the Tor Connection Assistant complains that normal bridges are not allowed 0.216

And I cannot click the "Connect to Tor" button 0.208

Hooks

After features/support/hooks.rb:326 0.954

After features/support/hooks.rb:100 0.042

Feature: Using Tor bridges and pluggable transports

Tags: @product

33.645

Scenario The same Tor configuration is applied when the network is reconnected

Steps

Given I configure a direct connection in the Tor Connection Assistant 8.901

And I wait until Tor is ready 4.581

When I disconnect the network through GNOME 3.732

And I connect the network through GNOME 3.686

Then the Tor Connection Assistant autostarts 3.954

And the Tor Connection Assistant connects to Tor 4.358

And I wait until Tor is ready 1.743

And Tor is using the same configuration as before 0.000

And available upgrades have been checked 0.107

And all Internet traffic has only flowed through Tor or connectivity check service 2.580

Hooks

After features/support/hooks.rb:326 0.798

After features/support/hooks.rb:100 0.040

Feature: Using Tor bridges and pluggable transports

Tags: @product

46.666

Scenario Reconnecting from an unblocked network to a blocked network displays an error

Steps

Given I configure a direct connection in the Tor Connection Assistant 7.747

And I wait until Tor is ready 4.054

And I disconnect the network through GNOME 3.262

And the Tor network and default bridges are blocked 1.711

When I connect the network through GNOME 3.314

Then the Tor Connection Assistant reports that it failed to connect 26.575

Hooks

After features/support/hooks.rb:326 0.826

After features/support/hooks.rb:100 0.044

Feature: Using Tor bridges and pluggable transports

Tags: @product

37.384

Scenario Tor Connection honors my choice of using default bridges on retry, too

Steps

Given the Tor network and default bridges are blocked 2.299

When I unsuccessfully configure some default bridges in the Tor Connection Assistant 23.666

Then the Tor Connection Assistant reports that it failed to connect 0.150

Given the Tor network and default bridges are unblocked 1.615

When I click "Connect to Tor" 1.225

Then I wait until Tor is ready 6.917

And Tor is configured to use the default bridges 0.599

And all Internet traffic has only flowed through the default bridges or connectivity check service 0.911

Hooks

After features/support/hooks.rb:326 1.438

After features/support/hooks.rb:100 0.037

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

22.297

Scenario Erasure of memory freed by killed userspace processes

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I prepare Tails for memory erasure tests 0.693

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

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

Output 1

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

When I kill the allocating process 0.313

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

1.588%

1.588% 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: 1.588% (14 MiB out of 890 MiB reference memory)

Hooks

After features/support/hooks.rb:326 5.407

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:29:14_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:29:14_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:29:14_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:29:14_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

27.590

Scenario Erasure of tmpfs data on unmount

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

And I prepare Tails for memory erasure tests 0.639

And I find very few patterns in the guest's memory 5.264

Output 1

Pattern coverage: 0.000% (0 MiB out of 884 MiB reference memory)

When I mount a 128 MiB tmpfs on "/mnt" and fill it with a known pattern 1.978

Then patterns cover at least 99% of the test FS size in the guest's memory 4.522

Output 1

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

When I umount "/mnt" 0.767

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 884 MiB reference memory)

Hooks

After features/support/hooks.rb:326 0.877

After features/support/hooks.rb:100 0.000

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

53.973

Scenario Erasure of read and write disk caches on unmount: vfat

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I prepare Tails for memory erasure tests 0.601

When I plug and mount a 128 MiB USB drive with a vfat filesystem 10.384

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 883 MiB reference memory)

# write cache

When I fill the USB drive with a known pattern 3.080

Then patterns cover at least 86% of the test FS size in the guest's memory 4.303

Output 1

Pattern coverage: 88.287% (112 MiB out of 127 MiB reference memory)

When I umount the USB drive 1.472

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 883 MiB reference memory)

# read cache

When I mount the USB drive again 0.290

And I read the content of the test FS 4.708

Then patterns cover at least 99% of the test FS size in the guest's memory 4.606

Output 1

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

When I umount the USB drive 0.626

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 883 MiB reference memory)

Hooks

After features/support/hooks.rb:326 1.482

After features/support/hooks.rb:100 0.000

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

1:21.730

Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I prepare Tails for memory erasure tests 0.673

When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 40.693

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 895 MiB reference memory)

# write cache

When I fill the USB drive with a known pattern 3.801

Then patterns cover at least 99% of the test FS size in the guest's memory 3.722

Output 1

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I umount the USB drive 1.084

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 895 MiB reference memory)

# read cache

When I mount the USB drive again 5.097

And I read the content of the test FS 1.033

Then patterns cover at least 99% of the test FS size in the guest's memory 3.698

Output 1

Pattern coverage: 106.116% (97 MiB out of 91 MiB reference memory)

When I umount the USB drive 1.067

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 895 MiB reference memory)

Hooks

After features/support/hooks.rb:326 1.989

After features/support/hooks.rb:100 0.000

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

1:6.306

Scenario Erasure of the overlayfs read-write branch on shutdown

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

And I prepare Tails for memory erasure tests 0.540

When I fill a 128 MiB file with a known pattern on the root filesystem 16.010

# ensure the pattern is in memory due to tmpfs, not to disk cache

And I drop all kernel caches 2.094

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

Output 1

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

When I trigger shutdown 0.015

And I wait 20 seconds 20.014

Output 1

Slept for 20 seconds

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 882 MiB reference memory)

Hooks

After features/support/hooks.rb:326 3.555

After features/support/hooks.rb:100 0.000

Feature: System memory erasure on shutdown

Tags: @product @slow @not_release_blocker

7:45.747

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

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173: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:326 6.285

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:41:03_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:41:03_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:41:03_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:41:03_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal

After features/support/hooks.rb:100 0.014

Feature: Installing Tails to a USB drive

Tags: @product @not_release_blocker

27.141

Scenario Try installing Tails to a too small USB drive with GPT and a FAT partition

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

And I temporarily create a 4 GiB disk named "gptfat" 0.085

And I create a gpt partition with a vfat filesystem on disk "gptfat" 6.392

And I plug USB drive "gptfat" 2.406

When I start Tails Installer 9.286

Then I am told by Tails Installer that the destination device "is too small" 0.048

Hooks

After features/support/hooks.rb:326 0.760

After features/support/hooks.rb:100 0.001

Feature: Installing Tails to a USB drive

Tags: @product

22.355

Scenario Detecting when a target USB drive is inserted or removed

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I temporarily create a 7200 MiB disk named "temp" 0.079

And I start Tails Installer 9.353

But a suitable USB device is not found 0.024

When I plug USB drive "temp" 3.038

Then the "temp" USB drive is selected 0.094

When I unplug USB drive "temp" 0.221

Then a suitable USB device is not found 0.031

Hooks

After features/support/hooks.rb:326 0.850

After features/support/hooks.rb:100 0.000

Feature: Installing Tails to a USB drive

Tags: @product

3:18.670

Scenario Installing Tails with Tails Installer to a used USB drive

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I temporarily create a 7200 MiB disk named "install" 0.080

And I create a gpt partition with a vfat filesystem on disk "install" 6.634

And I plug USB drive "install" 2.639

And I install Tails to USB drive "install" by cloning 2:22.206

Then the running Tails is installed on USB drive "install" 31.821

And there is a random seed on USB drive "install" 6.606

But there is no persistence partition on USB drive "install" 0.091

Hooks

After features/support/hooks.rb:326 1.272

After features/support/hooks.rb:100 0.096

Feature: Installing Tails to a USB drive

Tags: @product

2:35.944

Scenario Installing Tails with Tails Installer to a pristine USB drive

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I temporarily create a 7200 MiB disk named "install" 0.398

And I plug USB drive "install" 2.581

And I install Tails to USB drive "install" by cloning 2:2.635

Then the running Tails is installed on USB drive "install" 14.524

And there is a random seed on USB drive "install" 7.239

But there is no persistence partition on USB drive "install" 0.085

Hooks

After features/support/hooks.rb:326 1.691

After features/support/hooks.rb:100 0.124

Feature: Installing Tails to a USB drive

Tags: @product

2:12.728

Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage

Hooks

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 2:12.728

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I create a file in the Persistent directory 0.000

And I temporarily create a 7200 MiB disk named "install" 0.000

And I create a gpt partition with a vfat filesystem on disk "install" 0.000

And I plug USB drive "install" 0.000

And I install Tails with Persistent Storage to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is a persistence partition on USB drive "install" 0.000

And the USB drive "install" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:326 6.804

Output 1

SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 00:50:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:50:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:50:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:50:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:50:11_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:100 0.000

Feature: Installing Tails to a USB drive

Tags: @product

2:12.705

Scenario Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:57:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I temporarily create a 7200 MiB disk named "install" 0.000

And I plug USB drive "install" 0.000

And I install Tails to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is no persistence partition on USB drive "install" 0.000

Hooks

After features/support/hooks.rb:326 6.935

Output 1

SCENARIO FAILED: 'Installing Tails with Tails Installer to a pristine USB drive, without cloning the Persistent Storage' (at time 00:52:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:52:31_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:52:31_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:52:31_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:52:31_Installing_Tails_with_Tails_Installer_to_a_pristine_USB_drive,_without_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:100 0.000

Feature: Installing Tails to a USB drive

Tags: @product

2:9.828

Scenario Re-installing Tails over an existing USB installation with a persistent partition

Hooks

Before features/support/hooks.rb:269 0.004

Steps

# We reach this first checkpoint only to ensure that the ' __internal' disk has reached the state (Tails installed + persistent partition set up) we need before we clone it below.

# This first part is done without Tails Installer (install from Tails USB image)

# Note: the "__internal" disk will keep its state across scenarios

# and features until one of its snapshots is restored.

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_install.feature:70:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I have started Tails from DVD without network and logged in 0.000

And I clone USB drive "__internal" to a temporary USB drive "install" 0.000

And I plug USB drive "install" 0.000

# This second part is done with Tails Installer, that's what this scenario is about

When I reinstall Tails to USB drive "install" by cloning 0.000

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is no persistence partition on USB drive "install" 0.000

Hooks

After features/support/hooks.rb:326 6.838

Output 1

SCENARIO FAILED: 'Re-installing Tails over an existing USB installation with a persistent partition' (at time 00:54:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:54:48_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:54:48_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:54:48_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/00:54:48_Re-installing_Tails_over_an_existing_USB_installation_with_a_persistent_partition.journal

After features/support/hooks.rb:100 0.000

Feature: Installing Tails to a USB drive

Tags: @product @uefi

2:7.351

Scenario Booting Tails from a USB drive in UEFI mode

Hooks

Before features/support/hooks.rb:269 0.003

Steps

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

And I power off the computer 0.335

And the computer is set to boot in UEFI mode 0.030

When I start Tails from USB drive "__internal" with network unplugged and I login 1:50.421

Then Tails is running from USB drive "__internal" 0.359

And the boot device has safe access rights 2.909

And Tails has started in UEFI mode 0.056

Hooks

After features/support/hooks.rb:326 2.453

After features/support/hooks.rb:100 0.006

Feature: Installing Tails to a USB drive

Tags: @product

2:50.685

Scenario Installing Tails with GNOME Disks from a USB image

Hooks

Before features/support/hooks.rb:269 0.002

Steps

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

And I plug and mount a USB drive containing a Tails USB image 52.174

And I create a 7200 MiB disk named "usbimage" 0.164

And I plug USB drive "usbimage" 2.454

And I install a Tails USB image to the 7200 MiB disk with GNOME Disks 1:46.630

Hooks

After features/support/hooks.rb:326 3.539

After features/support/hooks.rb:100 0.098

Feature: Installing Tails to a USB drive

Tags: @product

1:40.169

Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied

Hooks

Before features/support/hooks.rb:269 0.003

Steps

Given a computer 0.298

And I start Tails from USB drive "usbimage" with network unplugged and I login 1:38.355

Then Tails is running from USB drive "usbimage" 0.411

And the label of the system partition on "usbimage" is "Tails" 0.360

And the system partition on "usbimage" is an EFI system partition 0.249

And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.142

And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.118

And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.128

And the system partition on "usbimage" has the expected flags 0.103

Hooks

After features/support/hooks.rb:326 1.374

After features/support/hooks.rb:100 0.006

Feature: Additional software

Tags: @product @check_tor_leaks @slow

5:30.793

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:269 0.004

Before features/support/hooks.rb:507 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 59.878

And I update APT using apt 19.587

And I install "popularity-contest" using apt 25.745

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

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

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

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

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

And I enable persistence 2:0.365

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:36:in `And I enable persistence'

And I log in to a new session 0.000

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:515 0.035

After features/support/hooks.rb:326 6.407

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:07:11)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:07:11_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:100 0.011

Feature: Additional software

Tags: @product @check_tor_leaks @slow

2:30.135

Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package

Hooks

Before features/support/hooks.rb:269 0.003

Before features/support/hooks.rb:507 0.003

Steps

Given a computer 0.202

And I start Tails from USB drive "__internal" and I login with an administration password 1:42.456

And I update APT using apt 17.381

When I install "makepp" using apt 25.623

Then the Additional Software dpkg hook has been run for package "makepp" and notices the persistence is locked 4.379

And the package "makepp" is installed 0.092

Hooks

After features/support/hooks.rb:515 43.680

After features/support/hooks.rb:326 1.112

After features/support/hooks.rb:100 0.019

Feature: Additional software

Tags: @product @check_tor_leaks @slow

3:0.585

Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.008

Steps

Given a computer 0.216

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:285: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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/additional_software_packages.feature:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'

When I uninstall "popularity-contest" using apt 0.000

And I accept removing "popularity-contest" from Additional Software 0.000

Then "popularity-contest" is not in the list of Additional Software 0.000

When I start Synaptic 0.000

And I update APT using Synaptic 0.000

And I install "cowsay" using Synaptic 0.000

And I accept adding "cowsay" to Additional Software 0.000

Then Additional Software is correctly configured for package "cowsay" 0.000

When I uninstall "cowsay" using apt 0.000

And I refuse removing "cowsay" from Additional Software 0.000

Then Additional Software is correctly configured for package "cowsay" 0.000

When I start "Additional Software" via GNOME Activities Overview 0.000

And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000

Then "cowsay" is not in the list of Additional Software 0.000

When I install "cowsay" using apt 0.000

And I refuse adding "cowsay" to Additional Software 0.000

Then "cowsay" is not in the list of Additional Software 0.000

Hooks

After features/support/hooks.rb:515 0.036

After features/support/hooks.rb:326 6.491

Output 1

SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 01:13:34)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume

Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt

Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt

Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:13:34_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal

After features/support/hooks.rb:100 0.011

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker

3:10.934

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:269 0.006

Before features/support/hooks.rb:507 0.008

Steps

Given a computer 0.445

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:285: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'

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

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

And I accept adding "cowsay" to Additional Software 0.000

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

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

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

And the network is plugged 0.000

And Tor is ready 0.000

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

And available upgrades have been checked 0.000

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

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

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:515 0.033

After features/support/hooks.rb:326 5.933

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:16:51)

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:16:51_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal

After features/support/hooks.rb:100 0.011

Feature: Additional software

Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited

3:3.063

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

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.005

Steps

Given a computer 0.195

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

And I enable persistence 2:0.397

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:126:in `And I enable persistence'

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

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

And I log in to a new session 0.000

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

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:515 0.038

After features/support/hooks.rb:326 6.153

Output 1

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

Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log

Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_I_am_notified_when_Additional_Software_fails_to_install_a_package.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:20:00_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal

After features/support/hooks.rb:100 0.010

Feature: Upgrading an old Tails USB installation

Tags: @product

2:15.552

Scenario Installing an old version of Tails to a pristine USB drive

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.260

And I create a 7200 MiB disk named "old" 0.053

And I plug USB drive "old" 1.058

And I write an old version of the Tails USB image to disk "old" 30.780

When I start Tails from USB drive "old" with network unplugged 1:39.135

Then the boot device has safe access rights 3.263

And Tails is running from USB drive "old" 0.327

And there is no persistence partition on USB drive "old" 0.067

And process "udev-watchdog" is running 0.098

And udev-watchdog is monitoring the correct device 0.302

And I unplug USB drive "old" 0.204

Hooks

After features/support/hooks.rb:326 7.128

After features/support/hooks.rb:100 0.008

Feature: Upgrading an old Tails USB installation

Tags: @product

2:21.716

Scenario Creating a persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:269 0.004

Steps

Given a computer 0.194

And I start Tails from USB drive "old" with network unplugged and I login 1:28.781

Then Tails is running from USB drive "old" 0.385

And I create a persistent partition 39.818

And I take note of which tps features are available 2.530

Then a Tails persistence partition exists on USB drive "old" 1.245

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

Hooks

After features/support/hooks.rb:326 0.151

After features/support/hooks.rb:100 0.009

Feature: Upgrading an old Tails USB installation

Tags: @product

3:9.877

Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given a computer 0.283

And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:9.594

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:285: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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

Hooks

After features/support/hooks.rb:326 6.531

Output 1

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:28:01)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:28:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:28:01_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:28:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:28:01_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal

After features/support/hooks.rb:100 0.009

Feature: Upgrading an old Tails USB installation

Tags: @product

3:0.403

Scenario Upgrading an old Tails USB installation from another Tails USB drive

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

And I log in to a new session 21.405

And I clone USB drive "old" to a new USB drive "to_upgrade" 1.471

And I plug USB drive "to_upgrade" 2.417

When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.496

Then the running Tails is installed on USB drive "to_upgrade" 31.304

And I unplug USB drive "to_upgrade" 0.368

And I unplug USB drive "__internal" 0.639

Hooks

After features/support/hooks.rb:326 3.600

After features/support/hooks.rb:100 0.000

Feature: Upgrading an old Tails USB installation

Tags: @product

3:5.326

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

Hooks

Before features/support/hooks.rb:269 0.004

Steps

Given a computer 0.650

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:285: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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:326 5.803

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:34:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:34:16_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:34:16_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:34:16_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:34:16_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.011

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

2:25.865

Scenario Upgrading an initial Tails installation with an incremental upgrade

Hooks

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 2:25.865

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And no SquashFS delta is installed 0.000

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

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

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

And the file system changes introduced in version 6.3~testoverlayfs are not present 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.2~testoverlayfs 0.000

And I can successfully install the incremental upgrade to version 6.2~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.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:326 6.496

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:36:48_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_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:36:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:36:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:36:48_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.000

Feature: Upgrading an old Tails USB installation

Tags: @product @automatic_upgrade

2:9.735

Scenario Upgrading a Tails whose signing key is outdated

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

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

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

And the signing key used by the Upgrader is outdated 0.000

But a current signing key is available on our website 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.2~testoverlayfs 0.000

Hooks

After features/support/hooks.rb:326 7.103

Output 1

SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:39:05)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:39:05_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:39:05_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:39:05_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:39:05_Upgrading_a_Tails_whose_signing_key_is_outdated.journal

After features/support/hooks.rb:100 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

1:0.636

Scenario Tails shuts down on DVD boot medium removal

Hooks

Before features/support/hooks.rb:269 0.004

Steps

Given I have started Tails from DVD and logged in and the network is connected 48.508

When I eject the boot medium 0.227

Then Tails eventually shuts down 11.900

Hooks

After features/support/hooks.rb:326 0.235

After features/support/hooks.rb:100 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

48.468

Scenario Tails erases memory on DVD boot medium removal: overlayfs read-write branch

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I prepare Tails for memory erasure tests 0.573

And I fill a 128 MiB file with a known pattern on the root filesystem 20.475

And patterns cover at least 128 MiB in the guest's memory 4.313

Output 1

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

When I eject the boot medium 0.377

And I wait for Tails to finish wiping the memory 11.144

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 885 MiB reference memory)

Hooks

After features/support/hooks.rb:326 3.631

After features/support/hooks.rb:100 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

39.881

Scenario Tails erases memory on DVD boot medium removal: vfat

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

And I prepare Tails for memory erasure tests 0.621

And I plug and mount a 128 MiB USB drive with a vfat filesystem 9.330

And I fill the USB drive with a known pattern 3.405

And I read the content of the test FS 0.138

And patterns cover at least 90% of the test FS size in the guest's memory 4.584

Output 1

Pattern coverage: 97.924% (124 MiB out of 127 MiB reference memory)

When I eject the boot medium 0.313

And I wait for Tails to finish wiping the memory 11.098

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 866 MiB reference memory)

Hooks

After features/support/hooks.rb:326 3.576

After features/support/hooks.rb:100 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

1:12.941

Scenario Tails erases memory on DVD boot medium removal: LUKS-encrypted ext4

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

And I prepare Tails for memory erasure tests 0.660

And I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 38.321

And I fill the USB drive with a known pattern 1.545

And I read the content of the test FS 0.083

And patterns cover at least 99% of the test FS size in the guest's memory 3.562

Output 1

Pattern coverage: 106.113% (97 MiB out of 91 MiB reference memory)

When I eject the boot medium 0.505

And I wait for Tails to finish wiping the memory 16.113

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

Output 1

Pattern coverage: 0.000% (0 MiB out of 888 MiB reference memory)

Hooks

After features/support/hooks.rb:326 3.620

After features/support/hooks.rb:100 0.000

Feature: Emergency shutdown

Tags: @product @not_release_blocker

2:11.239

Scenario Tails erases memory and shuts down on USB boot medium removal: persistent data

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/emergency_shutdown.feature:48: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

And I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000

And patterns cover at least 100 MiB in the guest's memory 0.000

When I eject the boot medium 0.000

And I wait for Tails to finish wiping the memory 0.000

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

And Tails eventually shuts down 0.000

Hooks

After features/support/hooks.rb:326 6.984

Output 1

SCENARIO FAILED: 'Tails erases memory and shuts down on USB boot medium removal: persistent data' (at time 01:45:16)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:45:16_Tails_erases_memory_and_shuts_down_on_USB_boot_medium_removal:_persistent_data.journal

After features/support/hooks.rb:100 0.000

Feature: APT sources are correctly configured

Tags: @product

58.682

Scenario APT sources are configured correctly

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.200

And I start Tails from DVD with network unplugged 58.091

Then the only hosts in APT sources are "cdn-fastly.deb.debian.org,deb.tails.boum.org,deb.torproject.org" 0.054

And no proposed-updates APT suite is enabled 0.062

And no experimental APT suite is enabled for deb.torproject.org 0.065

And if releasing, no unversioned Tails APT source is enabled 0.193

Output 1

Not on a tag ⇒ skipping this step

And if releasing, the tagged Tails APT source is enabled 0.014

Output 1

Not on a tag ⇒ skipping this step

Hooks

After features/support/hooks.rb:326 0.667

After features/support/hooks.rb:100 0.008

Feature: Backing up the persistent storage

Tags: @product

2:9.865

Scenario Using Tails' custom backup tool to backup a newly added file

Hooks

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 2:9.865

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/backup.feature:8:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

# The volume cannot be in use when GuestFs clones it, which we do below

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

And I clone USB drive "__internal" to a temporary USB drive "backup" 0.000

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

And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.000

When I start Tails' custom backup tool 0.000

Then the backup tool displays "Plug in your backup Tails USB stick" 0.000

When I plug USB drive "backup" 0.000

And I give the Persistent Storage on drive "backup" its own UUID 0.000

And I click "Retry" in the backup tool 0.000

Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.000

When I click "Back Up" in the backup tool 0.000

And I enter my persistent storage passphrase into the polkit prompt 0.000

Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 0.000

# The backup tool ejects the drive, so we have to replug it

When I unplug USB drive "backup" 0.000

And I plug USB drive "backup" 0.000

Then the USB drive "backup" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:326 6.080

Output 1

SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:48:33)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:48:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:48:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:48:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:48:33_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal

After features/support/hooks.rb:100 0.000

Feature: Getting a DHCP lease without leaking too much information

Tags: @product

0.218

Scenario Getting a DHCP lease with the default NetworkManager connection

Steps

Then the hostname should not have been leaked on the network 0.218

Hooks

After features/support/hooks.rb:326 0.724

After features/support/hooks.rb:100 0.066

Feature: Getting a DHCP lease without leaking too much information

Tags: @product

0.746

Scenario Getting a DHCP lease with a manually configured NetworkManager connection

Steps

When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.165

And I switch to the "manually-added-con" NetworkManager connection 0.364

Then the hostname should not have been leaked on the network 0.216

Hooks

After features/support/hooks.rb:326 0.613

After features/support/hooks.rb:100 0.042

Feature: Tails documentation

Tags: @product @doc @not_release_blocker

58.257

Scenario The Tails documentation launcher works when offline

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

When I start "Tails Documentation" via GNOME Activities Overview 11.070

Then the Tor Browser has started 24.280

Then "Tails - Documentation" has loaded in the Tor Browser 0.556

Hooks

After features/support/hooks.rb:326 1.141

After features/support/hooks.rb:100 0.000

Feature: Tails documentation

Tags: @product @doc @not_release_blocker

55.439

Scenario The Tails documentation launcher works when online

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 19.348

When I start "Tails Documentation" via GNOME Activities Overview 10.879

Then the Tor Browser has started 24.579

Then "Tails - Documentation" has loaded in the Tor Browser 0.632

Hooks

After features/support/hooks.rb:326 0.823

After features/support/hooks.rb:100 0.000

Feature: Electrum Bitcoin client

Tags: @product @check_tor_leaks

22.476

Scenario I am warned if Electrum is not persistent

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.004

Steps

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

When I start Electrum through the GNOME menu 11.322

But the "electrum" tps feature is not enabled 0.724

And I see a warning that Electrum is not persistent 1.615

Hooks

After features/support/hooks.rb:515 0.114

After features/support/hooks.rb:326 0.896

After features/support/hooks.rb:100 0.000

Feature: Using Evince

Tags: @product

21.192

Scenario I can view and print a PDF file stored in /usr/share

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

When I open "/usr/share/cups/data/default-testpage.pdf" with Evince 3.874

Then I see "CupsTestPage.png" after at most 40 seconds 3.256

And I can print the current document to "/home/amnesia/output.pdf" 4.796

Hooks

After features/support/hooks.rb:326 1.139

After features/support/hooks.rb:100 0.000

Feature: Using Evince

Tags: @product

22.663

Scenario I can view and print a PDF file stored in non-persistent /home/amnesia

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia" as user "amnesia" 0.174

When I open "/home/amnesia/default-testpage.pdf" with Evince 3.866

Then I see "CupsTestPage.png" after at most 40 seconds 3.555

And I can print the current document to "/home/amnesia/output.pdf" 6.184

Hooks

After features/support/hooks.rb:326 0.858

After features/support/hooks.rb:100 0.000

Feature: Using Evince

Tags: @product @not_release_blocker

23.389

Scenario I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg

Hooks

Before features/support/hooks.rb:269 0.004

Steps

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

And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.181

Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.043

And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.077

And the file "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.046

Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.149

When I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 3.656

Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 2.720

And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.093

When I close Evince 0.236

Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.113

When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 2.211

Then Evince tells me it cannot open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.323

And AppArmor has denied "/usr/bin/evince" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.071

When I close Evince 0.282

Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.145

When I try to open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 2.254

Then Evince tells me it cannot open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.861

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

Hooks

After features/support/hooks.rb:326 0.778

After features/support/hooks.rb:100 0.000

Feature: Using Evince

Tags: @product

2:9.209

Scenario I can view and print a PDF file stored in persistent /home/amnesia/Persistent

Hooks

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 2:9.209

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:45:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/Persistent" as user "amnesia" 0.000

Then the file "/home/amnesia/Persistent/default-testpage.pdf" exists 0.000

When I open "/home/amnesia/Persistent/default-testpage.pdf" with Evince 0.000

Then I see "CupsTestPage.png" after at most 40 seconds 0.000

And I can print the current document to "/home/amnesia/Persistent/output.pdf" 0.000

Hooks

After features/support/hooks.rb:326 6.616

Output 1

SCENARIO FAILED: 'I can view and print a PDF file stored in persistent /home/amnesia/Persistent' (at time 01:55:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:55:28_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:55:28_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:55:28_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:55:28_I_can_view_and_print_a_PDF_file_stored_in_persistent__home_amnesia_Persistent.journal

After features/support/hooks.rb:100 0.000

Feature: Using Evince

Tags: @product @not_release_blocker

2:9.786

Scenario I cannot view a PDF file stored in persistent /home/amnesia/.gnupg

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/evince.feature:54:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.000

Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.000

Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.000

And I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000

Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 0.000

And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.000

Hooks

After features/support/hooks.rb:326 6.886

Output 1

SCENARIO FAILED: 'I cannot view a PDF file stored in persistent /home/amnesia/.gnupg' (at time 01:57:44)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:57:44_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:57:44_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:57:44_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/01:57:44_I_cannot_view_a_PDF_file_stored_in_persistent__home_amnesia_.gnupg.journal

After features/support/hooks.rb:100 0.000

Feature: GNOME is well-integrated into Tails

Tags: @product @not_release_blocker

35.151

Scenario A screenshot is taken when the PRINTSCREEN key is pressed

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I wait 10 seconds 10.010

Output 1

Slept for 10 seconds

And there is no screenshot in the live user's Pictures directory 0.224

When I press the "PRINTSCREEN" key 0.120

And GNOME offers me various screenshot options 1.312

And I press the "Return" key 0.121

Then a screenshot is saved to the live user's Pictures directory 0.054

Hooks

After features/support/hooks.rb:326 0.794

After features/support/hooks.rb:100 0.000

Feature: GNOME is well-integrated into Tails

Tags: @product

9.254

Scenario GNOME notifications are shown to the user

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

When the "Dogtail rules!" notification is sent 0.296

Then the "Dogtail rules!" notification is shown to the user 0.542

Hooks

After features/support/hooks.rb:326 0.880

After features/support/hooks.rb:100 0.000

Feature: GNOME is well-integrated into Tails

Tags: @product

2:9.661

Scenario I can launch various apps via GNOME Activities Overview

Hooks

Before features/support/hooks.rb:269 0.006

Steps

# Some apps (Electrum and Persistent Storage Backup) only start when

# a Persistent Storage is available.

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/gnome.feature:22:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

# Some apps (Tor Browser) only start when the network is plugged.

And the network is plugged 0.000

And Tor is ready 0.000

And all notifications have disappeared 0.000

When I start "Additional Software" via GNOME Activities Overview 0.000

And I close the "tails-additional-software-config" window 0.000

When I start "Disks" via GNOME Activities Overview 0.000

# The close button of GNOME Disks is not accessible

And I close the "gnome-disks" window via Alt+F4 0.000

When I start "GNOME Terminal" via GNOME Activities Overview 0.000

And I close the "gnome-terminal-server" window 0.000

When I start "Files" via GNOME Activities Overview 0.000

And I close the "org.gnome.Nautilus" window 0.000

When I start "Persistent Storage" via GNOME Activities Overview 0.000

And I close the "tps-frontend" window 0.000

When I start "Persistent Storage Backup" via GNOME Activities Overview 0.000

And I close the "zenity" window 0.000

When I start "Pidgin" via GNOME Activities Overview 0.000

And I close the "Pidgin" window via Alt+F4 0.000

When I start "Thunderbird" via GNOME Activities Overview 0.000

And I close the "Thunderbird" window 0.000

When I start "Tor Browser" via GNOME Activities Overview 0.000

And I close the "Firefox" window 0.000

When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000

And I close the "unlock-veracrypt-volumes" window 0.000

When I start "Unsafe Browser" via GNOME Activities Overview 0.000

And I close the "Firefox" window 0.000

Hooks

After features/support/hooks.rb:326 6.343

Output 1

SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:00:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:00:47_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:00:47_I_can_launch_various_apps_via_GNOME_Activities_Overview.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:00:47_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:00:47_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal

After features/support/hooks.rb:100 0.000

Feature: Hardware failures

Tags: @product

41.465

Scenario Outline Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given a computer 0.954

And I start the computer from DVD with network unplugged 37.196

When Tails detects disk read failures on the SquashFS 0.248

Then I see a disk failure message on the splash screen 3.066

Hooks

After features/support/hooks.rb:326 0.663

After features/support/hooks.rb:100 0.011

Feature: Hardware failures

Tags: @product

41.948

Scenario Outline Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given a computer 0.279

And I start the computer from DVD with network unplugged 37.927

When Tails detects disk read failures on the boot device 0.981

Then I see a disk failure message on the splash screen 2.760

Hooks

After features/support/hooks.rb:326 0.788

After features/support/hooks.rb:100 0.012

Feature: Hardware failures

Tags: @product

42.481

Scenario Outline Alerting about disk read failures before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given a computer 0.270

And I start the computer from DVD with network unplugged 38.621

When Tails detects disk read failures on the boot device with a target error 1.031

Then I see a disk failure message on the splash screen 2.558

Hooks

After features/support/hooks.rb:326 0.691

After features/support/hooks.rb:100 0.018

Feature: Hardware failures

Tags: @product @doc

2:9.820

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:269 0.004

Steps

Given a computer 0.180

And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:9.640

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:27:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:21:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

When Tails detects disk read failures on the SquashFS 0.000

Then I see a disk failure message 0.000

Then I can open the hardware failure documentation from the disk failure message 0.000

Hooks

After features/support/hooks.rb:326 7.272

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:05:11)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:05:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:05:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:05:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:05:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal

After features/support/hooks.rb:100 0.000

Feature: Hardware failures

Tags: @product @doc

2:12.405

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.201

And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:12.204

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:28:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:21:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

When Tails detects disk read failures on the boot device 0.000

Then I see a disk failure message 0.000

Then I can open the hardware failure documentation from the disk failure message 0.000

Hooks

After features/support/hooks.rb:326 6.813

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:07:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:07:31_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:07:31_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:07:31_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:07:31_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal

After features/support/hooks.rb:100 0.000

Feature: Hardware failures

Tags: @product @doc

2:10.634

Scenario Outline Alerting about disk read failures in GNOME

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.240

And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:10.393

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/hardware_failure.feature:29:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
features/hardware_failure.feature:21:in `And I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

When Tails detects disk read failures on the boot device with a target error 0.000

Then I see a disk failure message 0.000

Then I can open the hardware failure documentation from the disk failure message 0.000

Hooks

After features/support/hooks.rb:326 6.753

Output 1

SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:09:49)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:09:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:09:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:09:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:09:49_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal

After features/support/hooks.rb:100 0.000

Feature: Hardware support

Tags: @product

53.072

Scenario Alerting about unsupported graphics card before reaching the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given a computer 0.208

And I start the computer from DVD with network unplugged and an unsupported graphics card 38.255

Then I see a graphics card failure message on the splash screen 14.609

Hooks

After features/support/hooks.rb:326 0.735

After features/support/hooks.rb:100 0.010

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

Tags: @product @doc

12.462

Scenario The included OpenPGP keys are up-to-date

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

Then the included OpenPGP keys are valid for the next 1 month 4.322

Hooks

After features/support/hooks.rb:326 0.718

After features/support/hooks.rb:100 0.000

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

Tags: @product

23.814

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

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

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

Hooks

After features/support/hooks.rb:326 0.761

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product

53.991

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.622

And I log in to a new session in German (de) 38.579

Then the amnesiac Documents directory exists 0.058

And there is a GNOME bookmark for the amnesiac Documents directory 2.731

Hooks

After features/support/hooks.rb:326 1.565

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product

51.259

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 10.318

And I log in to a new session in German (de) 38.230

Then the amnesiac Downloads directory exists 0.058

And there is a GNOME bookmark for the amnesiac Downloads directory 2.651

Hooks

After features/support/hooks.rb:326 0.830

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product

45.540

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.202

And I log in to a new session in German (de) 34.475

Then the amnesiac Music directory exists 0.069

And there is a GNOME bookmark for the amnesiac Music directory 2.793

Hooks

After features/support/hooks.rb:326 0.980

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product

46.936

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.461

And I log in to a new session in German (de) 35.484

Then the amnesiac Pictures directory exists 0.148

And there is a GNOME bookmark for the amnesiac Pictures directory 2.842

Hooks

After features/support/hooks.rb:326 0.800

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product

48.677

Scenario Outline Do not localize the XDG User Dirs to be able to use those dirs in Tor Browser (#19255)

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.294

And I log in to a new session in German (de) 36.448

Then the amnesiac Videos directory exists 0.184

And there is a GNOME bookmark for the amnesiac Videos directory 2.749

Hooks

After features/support/hooks.rb:326 1.254

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:26.209

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.477

When I log in to a new session in Arabic (ar) 35.651

Then the keyboard layout is set to "us" 0.214

When the network is plugged 0.050

And Tor is ready 16.777

Then I successfully start the Unsafe Browser in "ar" 15.314

And I kill the Unsafe Browser 5.922

When I enable the screen keyboard 0.102

Then the screen keyboard works in Tor Browser 32.570

And DuckDuckGo is the default search engine 10.275

And I kill the Tor Browser 5.684

And the screen keyboard works in Thunderbird 14.547

And the layout of the screen keyboard is set to "us" 0.621

Hooks

After features/support/hooks.rb:326 2.927

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:33.645

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.804

When I log in to a new session in Chinese (zh_CN) 33.964

Then the keyboard layout is set to "cn" 0.290

When the network is plugged 0.038

And Tor is ready 23.512

Then I successfully start the Unsafe Browser in "zh_CN" 16.713

And I kill the Unsafe Browser 5.771

When I enable the screen keyboard 0.106

Then the screen keyboard works in Tor Browser 29.855

And DuckDuckGo is the default search engine 10.673

And I kill the Tor Browser 5.727

And the screen keyboard works in Thunderbird 17.562

And the layout of the screen keyboard is set to "us" 0.624

Hooks

After features/support/hooks.rb:326 1.272

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:12.016

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.222

When I log in to a new session in English (en) 25.650

Then the keyboard layout is set to "us" 0.193

When the network is plugged 0.097

And Tor is ready 17.524

Then I successfully start the Unsafe Browser in "en" 17.067

And I kill the Unsafe Browser 5.603

When I enable the screen keyboard 0.113

Then the screen keyboard works in Tor Browser 31.618

And DuckDuckGo is the default search engine 5.578

And I kill the Tor Browser 5.308

And the screen keyboard works in Thunderbird 13.441

And the layout of the screen keyboard is set to "us" 0.596

Hooks

After features/support/hooks.rb:326 1.519

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:22.603

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 9.141

When I log in to a new session in French (fr) 33.532

Then the keyboard layout is set to "fr" 0.151

When the network is plugged 0.042

And Tor is ready 17.841

Then I successfully start the Unsafe Browser in "fr" 16.554

And I kill the Unsafe Browser 5.857

When I enable the screen keyboard 0.132

Then the screen keyboard works in Tor Browser 31.522

And DuckDuckGo is the default search engine 9.056

And I kill the Tor Browser 5.239

And the screen keyboard works in Thunderbird 12.889

And the layout of the screen keyboard is set to "fr" 0.641

Hooks

After features/support/hooks.rb:326 1.219

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:22.663

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.282

When I log in to a new session in German (de) 34.660

Then the keyboard layout is set to "de" 0.164

When the network is plugged 0.037

And Tor is ready 17.281

Then I successfully start the Unsafe Browser in "de" 16.464

And I kill the Unsafe Browser 5.952

When I enable the screen keyboard 0.116

Then the screen keyboard works in Tor Browser 30.484

And DuckDuckGo is the default search engine 9.361

And I kill the Tor Browser 5.296

And the screen keyboard works in Thunderbird 13.984

And the layout of the screen keyboard is set to "de" 0.576

Hooks

After features/support/hooks.rb:326 1.690

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:23.787

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.167

When I log in to a new session in Italian (it) 34.562

Then the keyboard layout is set to "it" 0.207

When the network is plugged 0.037

And Tor is ready 19.716

Then I successfully start the Unsafe Browser in "it" 14.921

And I kill the Unsafe Browser 5.931

When I enable the screen keyboard 0.113

Then the screen keyboard works in Tor Browser 30.056

And DuckDuckGo is the default search engine 10.341

And I kill the Tor Browser 5.636

And the screen keyboard works in Thunderbird 13.467

And the layout of the screen keyboard is set to "us" 0.627

Hooks

After features/support/hooks.rb:326 1.529

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:53.336

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.008

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.538

When I log in to a new session in Persian (fa) 37.329

Then the keyboard layout is set to "ir" 0.200

When the network is plugged 0.037

And Tor is ready 45.889

Then I successfully start the Unsafe Browser in "fa" 14.784

And I kill the Unsafe Browser 5.894

When I enable the screen keyboard 0.110

Then the screen keyboard works in Tor Browser 30.898

And DuckDuckGo is the default search engine 10.059

And I kill the Tor Browser 5.315

And the screen keyboard works in Thunderbird 13.695

And the layout of the screen keyboard is set to "ir" 0.582

Hooks

After features/support/hooks.rb:326 1.572

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:24.020

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.445

When I log in to a new session in Portuguese (pt) 37.812

Then the keyboard layout is set to "pt" 0.185

When the network is plugged 0.046

And Tor is ready 16.013

Then I successfully start the Unsafe Browser in "pt" 16.310

And I kill the Unsafe Browser 6.025

When I enable the screen keyboard 0.138

Then the screen keyboard works in Tor Browser 29.431

And DuckDuckGo is the default search engine 9.153

And I kill the Tor Browser 5.250

And the screen keyboard works in Thunderbird 14.634

And the layout of the screen keyboard is set to "us" 0.573

Hooks

After features/support/hooks.rb:326 1.205

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:25.723

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.199

When I log in to a new session in Russian (ru) 36.402

Then the keyboard layout is set to "ru" 0.366

When the network is plugged 0.051

And Tor is ready 18.435

Then I successfully start the Unsafe Browser in "ru" 16.141

And I kill the Unsafe Browser 5.817

When I enable the screen keyboard 0.091

Then the screen keyboard works in Tor Browser 30.719

And DuckDuckGo is the default search engine 9.882

And I kill the Tor Browser 5.341

And the screen keyboard works in Thunderbird 13.695

And the layout of the screen keyboard is set to "ru" 0.578

Hooks

After features/support/hooks.rb:326 1.435

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:28.426

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.008

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.779

When I log in to a new session in Spanish (es) 38.163

Then the keyboard layout is set to "es" 0.216

When the network is plugged 0.045

And Tor is ready 18.947

Then I successfully start the Unsafe Browser in "es" 15.786

And I kill the Unsafe Browser 5.830

When I enable the screen keyboard 0.130

Then the screen keyboard works in Tor Browser 28.990

And DuckDuckGo is the default search engine 10.510

And I kill the Tor Browser 5.745

And the screen keyboard works in Thunderbird 14.670

And the layout of the screen keyboard is set to "us" 0.611

Hooks

After features/support/hooks.rb:326 1.753

After features/support/hooks.rb:100 0.000

Feature: Localization

Tags: @product @doc @slow @not_release_blocker

2:30.829

Scenario Outline Tails is localized for every tier-1 language

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.580

When I log in to a new session in Turkish (tr) 34.866

Then the keyboard layout is set to "tr" 0.241

When the network is plugged 0.052

And Tor is ready 22.534

Then I successfully start the Unsafe Browser in "tr" 17.422

And I kill the Unsafe Browser 5.923

When I enable the screen keyboard 0.097

Then the screen keyboard works in Tor Browser 31.167

And DuckDuckGo is the default search engine 10.471

And I kill the Tor Browser 5.691

And the screen keyboard works in Thunderbird 13.223

And the layout of the screen keyboard is set to "us" 0.558

Hooks

After features/support/hooks.rb:326 1.503

After features/support/hooks.rb:100 0.000

Feature: Spoofing MAC addresses

Tags: @product

45.512

Scenario MAC address spoofing is disabled

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.332

And I capture all network traffic 0.005

When I disable MAC spoofing in Tails Greeter 4.004

And I log in to a new session 18.037

And the network is plugged 0.057

And Tor is ready 12.928

Then 1 network interface is enabled 0.109

And the 1st network device has its real MAC address configured 0.099

When I hotplug a network device and wait for it to be initialized 1.374

Then 2 network interfaces are enabled 0.123

And the 2nd network device has its real MAC address configured 0.109

And some network device leaked the real MAC address 0.331

Hooks

After features/support/hooks.rb:326 0.908

After features/support/hooks.rb:100 0.035

Feature: Spoofing MAC addresses

Tags: @product

45.308

Scenario MAC address spoofing is successful

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.095

And I capture all network traffic 0.007

When I log in to a new session 18.486

And the network is plugged 0.048

And Tor is ready 16.565

Then 1 network interface is enabled 0.134

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

When I hotplug a network device and wait for it to be initialized 1.425

Then 2 network interfaces are enabled 0.088

And the 2nd network device has a spoofed MAC address configured 0.094

And no network device leaked the real MAC address 0.276

Hooks

After features/support/hooks.rb:326 1.004

After features/support/hooks.rb:100 0.055

Feature: Spoofing MAC addresses

Tags: @product

32.557

Scenario MAC address spoofing fails and macchanger returns false

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.147

And I capture all network traffic 0.005

And the network is plugged 0.040

And macchanger will fail by not spoofing and always returns false 0.159

When I log in to a new session 22.107

Then no network interfaces are enabled 0.201

And no network device leaked the real MAC address 0.017

And I see the "Wired Network Disabled" notification after at most 60 seconds 1.877

Hooks

After features/support/hooks.rb:326 1.593

After features/support/hooks.rb:100 0.059

Feature: Spoofing MAC addresses

Tags: @product

31.128

Scenario MAC address spoofing fails and macchanger returns true

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.021

And I capture all network traffic 0.006

And the network is plugged 0.034

And macchanger will fail by not spoofing and always returns true 0.186

When I log in to a new session 17.826

Then no network interfaces are enabled 0.146

And no network device leaked the real MAC address 0.019

And I see the "Wired Network Disabled" notification after at most 60 seconds 1.885

Hooks

After features/support/hooks.rb:326 0.824

After features/support/hooks.rb:100 0.045

Feature: Spoofing MAC addresses

Tags: @product

31.845

Scenario MAC address spoofing fails and the module is not removed

Hooks

Before features/support/hooks.rb:269 0.008

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.627

And I capture all network traffic 0.009

And the network is plugged 0.047

And macchanger will fail by not spoofing and always returns true 0.189

And no network interface modules can be unloaded 0.652

When I log in to a new session 20.059

Then 1 network interface is enabled 0.141

But the MAC spoofing panic mode disabled networking 0.660

And no network device leaked the real MAC address 0.016

And I see the "All Networking Disabled" notification after at most 60 seconds 1.440

Hooks

After features/support/hooks.rb:326 0.994

After features/support/hooks.rb:100 0.030

Feature: Spoofing MAC addresses

Tags: @product

1:3.337

Scenario The MAC address is not leaked when booting Tails

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given a computer 0.244

And I capture all network traffic 0.005

When I start the computer 1.102

Then the computer boots Tails 1:1.828

And no network interfaces are enabled 0.143

And no network device leaked the real MAC address 0.012

Hooks

After features/support/hooks.rb:326 0.713

After features/support/hooks.rb:100 0.063

Feature: Metadata Anonymization Toolkit

Tags: @product @not_release_blocker

1:38.108

Scenario MAT can clean a PNG file

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given a computer 0.273

And I start Tails from DVD with network unplugged and I login 1:20.405

And I plug and mount a USB drive containing a sample PNG 15.695

Then MAT can clean some sample PNG file 1.734

Hooks

After features/support/hooks.rb:326 0.606

After features/support/hooks.rb:100 0.019

Feature: Networking

Tags: @product

1:21.950

Scenario No initial network

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I wait between 30 and 60 seconds 49.049

Output 1

Slept for 49 seconds

Then the Tor Status icon tells me that Tor is not usable 0.804

When the network is plugged 0.042

Then I successfully configure Tor 16.724

And the Tor Status icon tells me that Tor is usable 0.818

And all notifications have disappeared 4.667

And the time has synced 0.055

Hooks

After features/support/hooks.rb:326 0.707

After features/support/hooks.rb:100 0.000

Feature: Networking

Tags: @product @not_release_blocker

38.707

Scenario The Tails Greeter "disable all networking" option disables networking within Tails

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.423

And I disable networking in Tails Greeter 1.197

And I log in to a new session 18.462

Then no network interfaces are enabled 0.225

When I hotplug a network device 0.165

And I wait 10 seconds 10.003

Output 1

Slept for 10 seconds

Then no network interfaces are enabled 0.229

Hooks

After features/support/hooks.rb:326 1.034

After features/support/hooks.rb:100 0.000

Feature: Onion Circuits

Tags: @product

26.042

Scenario Onion Circuits shows some circuits

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.455

When I start "Onion Circuits" via GNOME Activities Overview 10.105

Then Onion Circuits starts 2.186

And Onion Circuits shows some circuits 0.294

Hooks

After features/support/hooks.rb:326 0.960

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:30.849

Scenario Tails Persistent Storage behave tests

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:43.357

And I update APT using apt 18.805

And I install "python3-behave" using apt 25.814

Then the Tails Persistent Storage behave tests pass 2.871

Hooks

After features/support/hooks.rb:326 0.648

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

41.521

Scenario Booting Tails from a USB drive with a disabled persistent partition

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

When I log in to a new session without activating the Persistent Storage 22.811

Then Tails is running from USB drive "__internal" 0.532

And persistence is disabled 0.298

But a Tails persistence partition exists on USB drive "__internal" 7.563

Hooks

After features/support/hooks.rb:326 1.131

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

4:10.629

Scenario Creating a Persistent Storage

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

Then Tails is running from USB drive "__internal" 0.451

When I create a file in the Persistent directory 0.141

And I create a persistent partition with the default settings 23.588

Then the file I created was copied to the Persistent Storage 0.832

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

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:285: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:285: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:26:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'

Then persistence for "Persistent" is active 0.000

And the file I created in the Persistent directory exists 0.000

Hooks

After features/support/hooks.rb:326 5.944

Output 1

SCENARIO FAILED: 'Creating a Persistent Storage' (at time 02:58:55)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:58:55_Creating_a_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:58:55_Creating_a_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:58:55_Creating_a_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/02:58:55_Creating_a_Persistent_Storage.journal

After features/support/hooks.rb:100 0.012

Feature: Tails persistence

Tags: @product

1:6.099

Scenario Creating a Persistent Storage when system is low on memory

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

And the system is very low on memory 6.811

When I create a file in the Persistent directory 1.256

When I try to create a persistent partition 26.403

Then The Persistent Storage app shows the error message "Not enough memory to create Persistent Storage" 0.464

When I close the Persistent Storage app 2.904

And I free up some memory 1.833

And I create a persistent partition with the default settings 14.005

Then the file I created was copied to the Persistent Storage 0.322

Hooks

After features/support/hooks.rb:326 1.652

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:11.026

Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it

Hooks

Before features/support/hooks.rb:269 0.009

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:42:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then Tails is running from USB drive "__internal" 0.000

And all tps features are active 0.000

And all persistent directories have safe access rights 0.000

When I disable the first tps feature 0.000

Then all tps features but the first one are active 0.000

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 and I login with persistence enabled 0.000

Then all tps features but the first one are active 0.000

Hooks

After features/support/hooks.rb:326 6.639

Output 1

SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 03:02:20)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:02:20_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:02:20_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:02:20_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:02:20_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:11.283

Scenario Activating and deactivating Persistent Storage features

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:53:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then persistence for "Persistent" is active 0.000

And I create a file in the Persistent directory 0.000

Then the file I created was copied to the Persistent Storage 0.000

When I disable the first tps feature 0.000

Then persistence for "Persistent" is not active 0.000

And the Persistent directory does not exist 0.000

When I enable the first tps feature 0.000

Then persistence for "Persistent" is active 0.000

And the file I created in the Persistent directory exists 0.000

Hooks

After features/support/hooks.rb:326 6.223

Output 1

SCENARIO FAILED: 'Activating and deactivating Persistent Storage features' (at time 03:04:37)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:04:37_Activating_and_deactivating_Persistent_Storage_features.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:04:37_Activating_and_deactivating_Persistent_Storage_features.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:04:37_Activating_and_deactivating_Persistent_Storage_features.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:04:37_Activating_and_deactivating_Persistent_Storage_features.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:9.891

Scenario Deleting data of a Persistent Storage feature

Hooks

Before features/support/hooks.rb:269 0.008

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:65:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then persistence for "Persistent" is active 0.000

When I create a file in the Persistent directory 0.000

And I disable the first tps feature 0.000

And I delete the data of the Persistent Folder feature 0.000

Then the file I created does not exist on the Persistent Storage 0.000

Hooks

After features/support/hooks.rb:326 6.458

Output 1

SCENARIO FAILED: 'Deleting data of a Persistent Storage feature' (at time 03:06:54)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:06:54_Deleting_data_of_a_Persistent_Storage_feature.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:06:54_Deleting_data_of_a_Persistent_Storage_feature.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:06:54_Deleting_data_of_a_Persistent_Storage_feature.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:06:54_Deleting_data_of_a_Persistent_Storage_feature.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:9.663

Scenario Writing files to a read/write-enabled persistent partition

Hooks

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 2:9.663

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:73:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And Tor is ready 0.000

And I take note of which tps features are available 0.000

When I write some files expected to persist 0.000

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

# XXX: The next step succeeds (and the --debug output confirms that it's actually looking for the files) but will fail in a subsequent scenario restoring the same snapshot. This exactly what we want, but why does it work? What is guestfs's behaviour when qcow2 internal snapshots are involved?

Then only the expected files are present on the persistence partition on USB drive "__internal" 0.000

Hooks

After features/support/hooks.rb:326 6.844

Output 1

SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 03:09:10)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:09:10_Writing_files_to_a_read_write-enabled_persistent_partition.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:09:10_Writing_files_to_a_read_write-enabled_persistent_partition.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:09:10_Writing_files_to_a_read_write-enabled_persistent_partition.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:09:10_Writing_files_to_a_read_write-enabled_persistent_partition.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:10.367

Scenario Creating and using a persistent NetworkManager connection

Hooks

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 2:10.367

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:83:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And Tor is ready 0.000

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

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

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

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:326 6.888

Output 1

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

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:11:27_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:11:27_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:11:27_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:11:27_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

1:41.628

Scenario Creating persistence from the Welcome Screen

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I enable persistence creation in Tails Greeter 1.128

And I log in to a new session expecting no warning about the Persistent Storage not being activated 24.990

Then I create a persistent partition with the default settings using the wizard that was already open 30.104

Hooks

After features/support/hooks.rb:326 2.253

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:10.462

Scenario Persistent Greeter options

Hooks

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 10.154

When I enable persistence 2:0.308

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:104:in `When I enable persistence'

Then no persistent Greeter options were restored 0.000

When I set all Greeter options to non-default values 0.000

And I log in to a new session in German (de) after having activated the Persistent Storage 0.000

Then all Greeter options are set to non-default values 0.000

When I cold reboot the computer 0.000

And the computer reboots Tails 0.000

Given I enable persistence 0.000

Then persistent Greeter options were restored 0.000

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

Then all Greeter options are set to non-default values 0.000

Hooks

After features/support/hooks.rb:326 7.244

Output 1

SCENARIO FAILED: 'Persistent Greeter options' (at time 03:15:28)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:15:28_Persistent_Greeter_options.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:15:28_Persistent_Greeter_options.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:15:28_Persistent_Greeter_options.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:15:28_Persistent_Greeter_options.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:11.461

Scenario Changing the Persistent Storage passphrase

Hooks

Before features/support/hooks.rb:269 0.010

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:117:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

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

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

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

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

Hooks

After features/support/hooks.rb:326 6.965

Output 1

SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:17:47)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:17:47_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:17:47_Changing_the_Persistent_Storage_passphrase.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:17:47_Changing_the_Persistent_Storage_passphrase.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:17:47_Changing_the_Persistent_Storage_passphrase.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

1:0.286

Scenario Deleting a Tails persistent partition

Hooks

Before features/support/hooks.rb:269 0.006

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

And I log in to a new session without activating the Persistent Storage 25.472

Then persistence is disabled 0.377

But a Tails persistence partition exists on USB drive "__internal" 7.665

And all notifications have disappeared 9.981

When I delete the persistent partition 6.569

Then there is no persistence partition on USB drive "__internal" 0.454

Hooks

After features/support/hooks.rb:326 1.122

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:10.626

Scenario Dotfiles persistence

Hooks

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 2:10.626

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/persistence.feature:136:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

When I write some dotfile expected to persist 0.000

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 and I login with persistence enabled 0.000

Then the expected persistent dotfile is present in the filesystem 0.000

Hooks

After features/support/hooks.rb:326 8.658

Output 1

SCENARIO FAILED: 'Dotfiles persistence' (at time 03:21:06)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:21:06_Dotfiles_persistence.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:21:06_Dotfiles_persistence.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:21:06_Dotfiles_persistence.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:21:06_Dotfiles_persistence.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:0.715

Scenario Feature activation fails

Hooks

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 9.753

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

When I try to enable persistence 0.305

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

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

And all notifications have disappeared 9.496

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

And all tps features are enabled 11.623

And all tps features but the first one are active 6.573

Hooks

After features/support/hooks.rb:326 1.422

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

10:17.338

Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage

Hooks

Before features/support/hooks.rb:269 0.009

Steps

Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 8:16.836

And I enable persistence 2:0.502

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:155:in `And I enable persistence'

And I log in to a new session after having activated the Persistent Storage 0.000

Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000

And persistence is enabled 0.000

Hooks

After features/support/hooks.rb:326 6.443

Output 1

SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 03:33:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:33:34_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:33:34_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:33:34_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:33:34_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:10.035

Scenario LUKS backup header is restored if something goes wrong during upgrade

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

And I enable persistence but something goes wrong during the LUKS header upgrade 2:0.609

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/usb.rb:718: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:718:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'

Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000

Hooks

After features/support/hooks.rb:326 5.918

Output 1

SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:35:51)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:35:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:35:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:35:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:35:51_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:16.202

Scenario Automatic filesystem repair

Hooks

Before features/support/hooks.rb:269 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.203

And I corrupt the Persistent Storage filesystem on USB drive "__internal" 6.428

When I enable persistence 2:0.570

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708: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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:168:in `When I enable persistence'

Then the filesystem of the Persistent Storage was repaired 0.000

Hooks

After features/support/hooks.rb:326 6.517

Output 1

SCENARIO FAILED: 'Automatic filesystem repair' (at time 03:38:13)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:38:13_Automatic_filesystem_repair.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:38:13_Automatic_filesystem_repair.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:38:13_Automatic_filesystem_repair.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:38:13_Automatic_filesystem_repair.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

2:32.859

Scenario Manual filesystem repair

Hooks

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 9.962

And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.548

When I try to enable persistence 0.621

Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 11.536

When I repair the filesystem of the Persistent Storage 1.281

Then the Welcome Screen tells me that the filesystem was repaired successfully 0.319

And the filesystem of the Persistent Storage was repaired 1.204

When I close the filesystem repair dialog 1.305

Then persistence is successfully enabled 2:0.079

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684: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/usb.rb:684:in `/^persistence is successfully enabled$/'
features/persistence.feature:180:in `Then persistence is successfully enabled'

Hooks

After features/support/hooks.rb:326 5.088

Output 1

SCENARIO FAILED: 'Manual filesystem repair' (at time 03:40:52)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:40:52_Manual_filesystem_repair.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:40:52_Manual_filesystem_repair.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:40:52_Manual_filesystem_repair.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:40:52_Manual_filesystem_repair.journal

After features/support/hooks.rb:100 0.000

Feature: Tails persistence

Tags: @product

23.674

Scenario Filesystem and I/O errors

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 5.967

And Tails detects disk read failures on the boot device 1.564

When I try to enable persistence 0.406

Then the Welcome Screen tells me that my hardware is probably failing 5.712

Hooks

After features/support/hooks.rb:326 0.777

After features/support/hooks.rb:100 0.000

Feature: Using persistent Tor bridges and pluggable transports

Tags: @product

0.000

Scenario Using Persistent Tor bridges

Steps

When I choose to connect to Tor automatically 0.000

And I accept Tor Connection's offer to use my persistent bridges 0.000

And I click "Connect to Tor" 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes the configured bridges 0.000

And the "TorConfiguration" tps feature is enabled and active 0.000

And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000

Hooks

After features/support/hooks.rb:326 6.119

Output 1

SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 03:45:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:45:41_Using_Persistent_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:45:41_Using_Persistent_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:45:41_Using_Persistent_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:45:41_Using_Persistent_Tor_bridges.journal

After features/support/hooks.rb:100 0.011

Feature: Using persistent Tor bridges and pluggable transports

Tags: @product

0.000

Scenario Disabling persistence of Tor bridges

Steps

When I choose to connect to Tor automatically 0.000

And I accept Tor Connection's offer to use my persistent bridges 0.000

And I disable saving bridges to Persistent Storage 0.000

And I configure a direct connection in the Tor Connection Assistant 0.000

Then I wait until Tor is ready 0.000

And tca.conf includes no bridge 0.000

And the "TorConfiguration" tps feature is not enabled and not active 0.000

And all Internet traffic has only flowed through Tor or connectivity check service 0.000

Hooks

After features/support/hooks.rb:326 6.467

Output 1

SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 03:50:03)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:50:03_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:50:03_Disabling_persistence_of_Tor_bridges.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:50:03_Disabling_persistence_of_Tor_bridges.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:50:03_Disabling_persistence_of_Tor_bridges.journal

After features/support/hooks.rb:100 0.010

Feature: Random Seed

Tags: @product

3:11.829

Scenario A random seed is read during boot and written during boot and shutdown

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given a computer 0.191

And I temporarily create a 7200 MiB disk named "temp" 0.052

And I plug USB drive "temp" 1.051

And I write the Tails USB image to disk "temp" 37.020

Then there is no random seed on USB drive "temp" 7.105

When I start Tails from USB drive "temp" with network unplugged 1:45.676

Then the random seed was written multiple times on first boot 0.105

And there is a random seed on USB drive "temp" 5.996

When I log in to a new session 17.149

And I wait for the random seed to be updated 1.073

Then there is a random seed on USB drive "temp" 6.160

And the random seed is different from the previous one 0.000

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

Then there is a random seed on USB drive "temp" 5.983

And the random seed is different from the previous one 0.000

Hooks

After features/support/hooks.rb:326 0.159

After features/support/hooks.rb:100 0.128

Feature: Tails has a sane default configuration

Tags: @product

12.596

Scenario The live user is setup correctly

Hooks

Before features/support/hooks.rb:269 0.008

Steps

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

Then the live user has been setup by live-boot 0.268

And the live user is a member of only its own group and "cdrom dialout floppy video plugdev netdev scanner lp lpadmin users" 0.099

And the live user owns its home directory which has strict permissions 0.253

Hooks

After features/support/hooks.rb:326 0.836

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product @not_release_blocker

18.693

Scenario No unexpected network services

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 18.426

Then no unexpected services are listening for network connections 0.266

Output 1

Service 'cups-browsed' is listening on 0.0.0.0:631 but has an exception

Service 'tor' is listening on 10.200.1.1:9050 but has an exception

Service 'onion-grater' is listening on 0.0.0.0:951 but has an exception

Hooks

After features/support/hooks.rb:326 0.867

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product

21.445

Scenario The live user can only access the expected local services

Hooks

Before features/support/hooks.rb:269 0.009

Steps

Given I have started Tails from DVD and logged in and the network is connected 15.216

Then the live user can only access allowed local services 6.229

Output 1

amnesia could access tor on 127.0.0.1:5353 (UDP) as expected
amnesia could access cups-browsed on 0.0.0.0:631 (UDP) as expected
amnesia could access tor on 10.200.1.1:9050 (TCP) as expected
amnesia could access onion-grater on 0.0.0.0:951 (TCP) as expected
amnesia could access cupsd on 127.0.0.1:631 (TCP) as expected
amnesia could access tor on 127.0.0.1:9062 (TCP) as expected
amnesia could not access tor on 127.0.0.1:9063 (TCP) as expected
amnesia could not access tor on 127.0.0.1:9052 (TCP) as expected
amnesia could access tor on 127.0.0.1:9050 (TCP) as expected
amnesia could access tor on 127.0.0.1:9040 (TCP) as expected

Hooks

After features/support/hooks.rb:326 0.903

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product

12.293

Scenario No unexpected error messages in the journal after booting from DVD

Hooks

Before features/support/hooks.rb:269 0.013

Steps

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

Then there are no unexpected messages of priority "err" or higher in the journal 0.070

Hooks

After features/support/hooks.rb:326 0.876

After features/support/hooks.rb:100 0.000

Feature: Tails has a sane default configuration

Tags: @product

2:10.931

Scenario No unexpected error messages in the journal after booting from USB drive

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/sane_defaults.feature:24:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

Then there are no unexpected messages of priority "err" or higher in the journal 0.000

Hooks

After features/support/hooks.rb:326 7.659

Output 1

SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 03:56:41)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:56:41_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:56:41_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:56:41_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/03:56:41_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal

After features/support/hooks.rb:100 0.000

Feature: Shutdown buttons in the system menu

Tags: @product

24.915

Scenario I can shutdown Tails via the system menu

Hooks

Before features/support/hooks.rb:269 0.010

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.275

When I request a shutdown using the system menu 1.857

Then Tails eventually shuts down 8.782

Hooks

After features/support/hooks.rb:326 0.189

After features/support/hooks.rb:100 0.000

Feature: Shutdown buttons in the system menu

Tags: @product @not_release_blocker

2:3.224

Scenario I can reboot Tails via the system menu

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 25.760

When I request a reboot using the system menu 1.751

Then Tails eventually restarts 1:35.712

Hooks

After features/support/hooks.rb:326 3.497

After features/support/hooks.rb:100 0.000

Feature: Logging in via SSH

Tags: @product @check_tor_leaks

7.593

Scenario Connecting to an SSH server on the Internet works and uses the default SocksPort

Steps

Given I monitor the network connections of SSH 0.083

And I have the SSH key pair for an SSH server 0.436

When I connect to an SSH server on the Internet 5.583

Then I have sucessfully logged into the SSH server 1.466

And I see that SSH is properly stream isolated 0.023

Hooks

After features/support/hooks.rb:515 0.525

After features/support/hooks.rb:326 1.027

After features/support/hooks.rb:100 0.000

Feature: Logging in via SSH

Tags: @product @check_tor_leaks

7.791

Scenario Connecting to an SSH server on the LAN

Steps

Given I have the SSH key pair for an SSH server 0.258

And an SSH server is running on the LAN 0.826

When I connect to an SSH server on the LAN 5.054

Then I am prompted to verify the SSH fingerprint for the SSH server 1.651

Hooks

After features/support/hooks.rb:515 0.342

After features/support/hooks.rb:326 0.622

After features/support/hooks.rb:100 0.001

Feature: Logging in via SSH

Tags: @product @check_tor_leaks @not_release_blocker

15.674

Scenario Connecting to an SFTP server on the Internet using the GNOME "Connect to Server" feature

Steps

Given I have the SSH key pair for an SFTP server 0.275

When I connect to an SFTP server on the Internet 14.392

Then I successfully connect to the SFTP server 1.007

Hooks

After features/support/hooks.rb:515 0.491

After features/support/hooks.rb:326 1.390

After features/support/hooks.rb:100 0.000

Feature: Thunderbird email client

Tags: @product @check_tor_leaks

17.543

Scenario No add-ons are installed

Steps

Given I cancel setting up an email account 3.694

When I open Thunderbird's Add-ons Manager 2.015

And I open the Extensions tab 1.108

Then I see that no add-ons are enabled in Thunderbird 10.724

Hooks

After features/support/hooks.rb:515 0.754

After features/support/hooks.rb:326 1.122

After features/support/hooks.rb:100 0.000

Feature: Thunderbird email client

Tags: @product @check_tor_leaks

45.572

Scenario I can send emails, and receive emails over IMAP

Steps

When I enter my email credentials into the autoconfiguration wizard 10.325

Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.454

And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.378

When I accept the autoconfiguration wizard's configuration 19.444

And I send an email to myself 6.561

And I fetch my email 1.494

Then I can find the email I sent to myself in my inbox 6.914

Hooks

After features/support/hooks.rb:515 1.536

After features/support/hooks.rb:326 1.057

After features/support/hooks.rb:100 0.000

Feature: Tor Connection helps the user in connecting to Tor

Tags: @product @not_release_blocker

14.205

Scenario Bridges are not enabled in automatic mode when going back from hiding Tor

Steps

When the network is plugged 0.320

And the Tor Connection Assistant autostarts 7.691

And I look at the hide mode but then I go back 4.756

And I choose to connect to Tor automatically 1.294

Then Tor Connection does not propose me to use Tor bridges 0.141

Hooks

After features/support/hooks.rb:326 1.312

After features/support/hooks.rb:100 0.000

Feature: Tor Connection helps the user in connecting to Tor

Tags: @product

1:29.392

Scenario I can use a network with captive portal

Steps

Given the Tor network and default bridges are blocked 1.954

And the network is plugged 0.206

And I make sure time sync before Tor connects indicates a captive portal 1.216

And the Tor Connection Assistant autostarts 2.585

When I choose to connect to Tor automatically 2.800

And I click "Connect to Tor" 1.159

Then the Tor Connection Assistant fails to connect to Tor 27.086

And the Tor Connection Assistant knows that it's not the time sync that failed 10.591

And the Tor Connection Assistant knows that there might be a captive portal 0.136

When I open the Unsafe Browser from Tor Connection 17.294

And I log-in to the Captive Portal 13.188

And I close the Unsafe Browser 0.121

And the Tor network and default bridges are unblocked 2.076

And I allow time sync before Tor connects to work again 0.064

And I click "Connect to Tor" 1.152

Then I wait until Tor is ready 7.755

Hooks

After features/support/hooks.rb:326 0.920

After features/support/hooks.rb:100 0.000

Feature: The Tor enforcement is effective

Tags: @product

12.621

Scenario The firewall configuration is very restrictive

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.061

Then the firewall's policy is to drop all IPv4 traffic 0.152

And the firewall is configured to only allow the clearnet and debian-tor users to connect directly to the Internet over IPv4 0.253

And the firewall's NAT rules only redirect traffic for the Unsafe Browser, Tor's TransPort, and DNSPort 0.090

And the firewall is configured to block all external IPv6 traffic 0.063

Hooks

After features/support/hooks.rb:326 0.628

After features/support/hooks.rb:100 0.000

Feature: The Tor enforcement is effective

Tags: @product

45.258

Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.151

And I capture all network traffic 0.006

When I successfully start the Unsafe Browser 18.931

And I open the Tails homepage in the Unsafe Browser 11.852

And the Tails homepage loads in the Unsafe Browser 0.629

Then the firewall leak detector has detected leaks 0.687

Hooks

After features/support/hooks.rb:326 1.197

After features/support/hooks.rb:100 0.043

Feature: The Tor enforcement is effective

Tags: @product

17.159

Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 15.975

And I capture all network traffic 0.006

And I disable Tails' firewall 0.279

When I do a TCP DNS lookup of "torproject.org" 0.801

Then the firewall leak detector has detected leaks 0.096

Hooks

After features/support/hooks.rb:326 0.792

After features/support/hooks.rb:100 0.035

Feature: The Tor enforcement is effective

Tags: @product

15.841

Scenario Anti test: Detecting UDP leaks of DNS lookups with the firewall leak detector

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.680

And I capture all network traffic 0.006

And I disable Tails' firewall 0.277

When I do a UDP DNS lookup of "torproject.org" 0.762

Then the firewall leak detector has detected leaks 0.112

Hooks

After features/support/hooks.rb:326 0.651

After features/support/hooks.rb:100 0.060

Feature: The Tor enforcement is effective

Tags: @product

17.628

Scenario Anti test: Detecting ICMP leaks of ping with the firewall leak detector

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.996

And I capture all network traffic 0.009

And I disable Tails' firewall 0.292

When I send some ICMP pings 4.174

Then the firewall leak detector has detected leaks 0.156

Hooks

After features/support/hooks.rb:326 0.708

After features/support/hooks.rb:100 0.035

Feature: The Tor enforcement is effective

Tags: @product @check_tor_leaks

14.409

Scenario The Tor enforcement is effective at blocking untorified TCP connection attempts

Hooks

Before features/support/hooks.rb:269 0.045

Before features/support/hooks.rb:507 0.019

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.974

When I open an untorified TCP connection to 1.2.3.4 on port 42 1.361

Then the untorified connection fails 0.000

And the untorified connection is logged as dropped by the firewall 0.073

Hooks

After features/support/hooks.rb:515 0.333

After features/support/hooks.rb:326 0.944

After features/support/hooks.rb:100 0.000

Feature: The Tor enforcement is effective

Tags: @product @check_tor_leaks

15.577

Scenario The Tor enforcement is effective at blocking untorified UDP connection attempts

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.018

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.180

When I open an untorified UDP connection to 1.2.3.4 on port 42 1.316

Then the untorified connection fails 0.000

And the untorified connection is logged as dropped by the firewall 0.080

Hooks

After features/support/hooks.rb:515 0.242

After features/support/hooks.rb:326 0.778

After features/support/hooks.rb:100 0.000

Feature: The Tor enforcement is effective

Tags: @product @check_tor_leaks

17.739

Scenario The Tor enforcement is effective at blocking untorified ICMP connection attempts

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.258

When I open an untorified ICMP connection to 1.2.3.4 5.396

Then the untorified connection fails 0.000

And the untorified connection is logged as dropped by the firewall 0.083

Hooks

After features/support/hooks.rb:515 0.297

After features/support/hooks.rb:326 0.653

After features/support/hooks.rb:100 0.000

Feature: The Tor enforcement is effective

Tags: @product

23.603

Scenario The system DNS is always set up to use Tor's DNSPort

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

And the system DNS is using the local DNS resolver 0.014

And the network is plugged 0.039

And I successfully configure Tor 15.167

Then the system DNS is still using the local DNS resolver 0.013

Hooks

After features/support/hooks.rb:326 1.596

After features/support/hooks.rb:100 0.000

Feature: Tor stream isolation is effective

Tags: @product @check_tor_leaks @not_release_blocker

10.203

Scenario tails-security-check is using the Tails-specific SocksPort

Steps

When I monitor the network connections of tails-security-check 0.057

And I re-run tails-security-check 0.127

Then I see that tails-security-check is properly stream isolated after 10 seconds 10.018

Hooks

After features/support/hooks.rb:515 0.612

After features/support/hooks.rb:326 0.838

After features/support/hooks.rb:100 0.000

Feature: Tor stream isolation is effective

Tags: @product @check_tor_leaks @not_release_blocker

2.481

Scenario htpdate is using the Tails-specific SocksPort

Steps

When I monitor the network connections of htpdate 0.072

And I re-run htpdate 2.396

Then I see that htpdate is properly stream isolated 0.013

Hooks

After features/support/hooks.rb:515 0.389

After features/support/hooks.rb:326 1.508

After features/support/hooks.rb:100 0.000

Feature: Tor stream isolation is effective

Tags: @product @check_tor_leaks @not_release_blocker

32.309

Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort

Steps

When I monitor the network connections of tails-upgrade-frontend-wrapper 0.080

And I re-run tails-upgrade-frontend-wrapper 32.211

Then I see that tails-upgrade-frontend-wrapper is properly stream isolated 0.016

Hooks

After features/support/hooks.rb:515 0.527

After features/support/hooks.rb:326 0.912

After features/support/hooks.rb:100 0.000

Feature: Tor stream isolation is effective

Tags: @product @check_tor_leaks

27.600

Scenario The Tor Browser is using the web browser-specific SocksPort

Steps

When I monitor the network connections of Tor Browser 0.070

And I start the Tor Browser 26.756

And the Tor Browser loads the startup page 0.738

Then I see that Tor Browser is properly stream isolated 0.034

Hooks

After features/support/hooks.rb:515 0.872

After features/support/hooks.rb:326 1.434

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

50.986

Scenario The Tor Browser cannot access the LAN

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.473

And a web server is running on the LAN 1.044

And I capture all network traffic 0.006

When I start the Tor Browser 25.236

And the Tor Browser loads the startup page 0.988

And I open a page on the LAN web server in the Tor Browser 10.034

Then the Tor Browser shows the "Unable to connect" error 0.843

And no traffic was sent to the web server on the LAN 0.358

Hooks

After features/support/hooks.rb:326 1.051

After features/support/hooks.rb:100 0.034

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

58.807

Scenario The Tor Browser directory is usable

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.814

Then the amnesiac Tor Browser directory exists 0.051

And there is a GNOME bookmark for the amnesiac Tor Browser directory 1.840

And the persistent Tor Browser directory does not exist 0.076

When I start the Tor Browser 24.913

And the Tor Browser loads the startup page 0.925

Then I can save the current page as "index.html" to the default downloads directory 5.429

And I can print the current page as "output.pdf" to the default downloads directory 11.755

Hooks

After features/support/hooks.rb:515 1.142

After features/support/hooks.rb:326 0.799

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

53.494

Scenario Downloading files with the Tor Browser

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.941

When I start the Tor Browser 24.888

Then the Tor Browser loads the startup page 1.024

When I download some file in the Tor Browser 13.258

Then the file is saved to the default Tor Browser download directory 0.380

Hooks

After features/support/hooks.rb:515 2.118

After features/support/hooks.rb:326 0.741

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

1:27.927

Scenario Playing an Ogg audio track

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.672

When I start the Tor Browser 27.335

And the Tor Browser loads the startup page 0.876

Then I can listen to an Ogg audio track in Tor Browser 47.042

Hooks

After features/support/hooks.rb:515 2.113

After features/support/hooks.rb:326 1.835

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

52.869

Scenario Watching a WebM video

Hooks

Before features/support/hooks.rb:269 0.006

Before features/support/hooks.rb:507 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.497

When I start the Tor Browser 24.009

And the Tor Browser loads the startup page 0.876

Then I can watch a WebM video in Tor Browser 14.485

Hooks

After features/support/hooks.rb:515 1.027

After features/support/hooks.rb:326 4.204

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:22.037

Scenario I can view a file stored in "~/Tor Browser" but not in ~/.gnupg

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.494

And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Tor Browser/synaptic.html" as user "amnesia" 0.121

And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.059

And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.077

Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.056

And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.054

And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.066

And the file "/tmp/synaptic.html" exists 0.045

Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.129

When I start the Tor Browser 27.329

And the Tor Browser loads the startup page 0.922

And I open the address "file:///home/amnesia/Tor Browser/synaptic.html" in the Tor Browser 11.133

Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.559

And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Tor Browser/synaptic.html" 0.189

Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.170

When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 6.108

Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.532

And AppArmor has denied "torbrowser_firefox" from opening "/home/amnesia/.gnupg/synaptic.html" 0.100

Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.125

When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 5.981

Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.581

And AppArmor has denied "torbrowser_firefox" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" 0.066

Given I restart monitoring the AppArmor log of "torbrowser_firefox" 0.128

When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 6.520

Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.567

# Due to our AppArmor aliases, /live/overlay will be treated

# as /lib/live/mount/overlay.

And AppArmor has denied "torbrowser_firefox" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" 0.071

# We do not get any AppArmor log for when access to files in /tmp is denied

# since we explictly override (commit 51c0060) the rules (from the user-tmp

# abstraction) that would otherwise allow it, and we do so with "deny", which

# also specifies "noaudit". We could explicitly specify "audit deny" and

# then have logs, but it could be a problem when we set up desktop

# notifications for AppArmor denials (#9337).

When I open the address "file:///tmp/synaptic.html" in the Tor Browser 6.323

Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.519

Hooks

After features/support/hooks.rb:326 2.039

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

38.491

Scenario The Tor Browser uses TBB's shared libraries

Hooks

Before features/support/hooks.rb:269 0.010

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.153

When I start the Tor Browser 23.131

Then the Tor Browser uses all expected TBB shared libraries 1.206

Hooks

After features/support/hooks.rb:326 1.691

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product @check_tor_leaks

1:2.539

Scenario The Tor Browser's "New identity" feature works as expected

Hooks

Before features/support/hooks.rb:269 0.005

Before features/support/hooks.rb:507 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.930

When I start the Tor Browser 25.431

And the Tor Browser loads the startup page 1.042

And I open the Tails homepage in the Tor Browser 10.562

Then the Tor Browser loads the Tails homepage 1.112

When I request a new identity in Tor Browser 3.194

Then the Tor Browser restarts into a fresh session 6.265

Hooks

After features/support/hooks.rb:515 2.081

After features/support/hooks.rb:326 2.401

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

53.064

Scenario The Tor Browser's circuit view feature works as expected

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 26.513

When I start the Tor Browser 23.842

And the Tor Browser loads the startup page 0.989

Then Tor Browser's circuit view is working 1.718

Hooks

After features/support/hooks.rb:326 3.517

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

1:2.202

Scenario WebRTC is disabled in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.760

When I start the Tor Browser 26.112

And the Tor Browser loads the startup page 1.054

When I open the address "https://net.ipcalf.com/" in the Tor Browser 10.205

Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page 0.891

When I open the address "https://mozilla.github.io/webrtc-landing/pc_test.html" in the Tor Browser 8.997

Then Tor Browser displays a "RTCPeerConnection is missing!" heading on the "Simple RTCPeerConnection Video Test" page 1.181

Hooks

After features/support/hooks.rb:326 0.929

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

2:10.410

Scenario The persistent Tor Browser directory is usable

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:119:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And the network is plugged 0.000

And I successfully configure Tor 0.000

And available upgrades have been checked 0.000

And all notifications have disappeared 0.000

Then the persistent Tor Browser directory exists 0.000

And there is a GNOME bookmark for the persistent Tor Browser directory 0.000

When I start the Tor Browser 0.000

And I open the address "https://tails.net/about" in the Tor Browser 0.000

And "Tails - How Tails works" has loaded in the Tor Browser 0.000

Then I can save the current page as "index.html" to the persistent Tor Browser directory 0.000

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

Hooks

After features/support/hooks.rb:326 6.707

Output 1

SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:23:03)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:23:03_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:23:03_The_persistent_Tor_Browser_directory_is_usable.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:23:03_The_persistent_Tor_Browser_directory_is_usable.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:23:03_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

47.901

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

Then the amnesiac Documents directory exists 0.067

And there is a GNOME bookmark for the amnesiac Documents directory 1.918

Then I start the Tor Browser in offline mode 26.897

And I can save the current page as "index.html" to the Documents GNOME bookmark 9.668

Hooks

After features/support/hooks.rb:326 0.897

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

46.521

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.008

Steps

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

Then the amnesiac Downloads directory exists 0.179

And there is a GNOME bookmark for the amnesiac Downloads directory 1.937

Then I start the Tor Browser in offline mode 26.722

And I can save the current page as "index.html" to the Downloads GNOME bookmark 8.489

Hooks

After features/support/hooks.rb:326 1.140

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

47.559

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.007

Steps

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

Then the amnesiac Music directory exists 0.132

And there is a GNOME bookmark for the amnesiac Music directory 1.929

Then I start the Tor Browser in offline mode 26.723

And I can save the current page as "index.html" to the Music GNOME bookmark 8.906

Hooks

After features/support/hooks.rb:326 1.181

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

46.287

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.008

Steps

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

Then the amnesiac Pictures directory exists 0.138

And there is a GNOME bookmark for the amnesiac Pictures directory 2.295

Then I start the Tor Browser in offline mode 26.918

And I can save the current page as "index.html" to the Pictures GNOME bookmark 8.514

Hooks

After features/support/hooks.rb:326 1.977

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

46.708

Scenario Outline The default XDG directories are usable in Tor Browser

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

Then the amnesiac Videos directory exists 0.061

And there is a GNOME bookmark for the amnesiac Videos directory 1.494

Then I start the Tor Browser in offline mode 26.648

And I can save the current page as "index.html" to the Videos GNOME bookmark 9.922

Hooks

After features/support/hooks.rb:326 0.910

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Tor Browser

Tags: @product

2:9.641

Scenario Persistent browser bookmarks

Hooks

Before features/support/hooks.rb:269 0.005

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/torified_browsing.feature:149:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And all tps features are active 0.000

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 have safe access rights 0.000

When I start the Tor Browser in offline mode 0.000

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

And I cold reboot the computer 0.000

And the computer reboots Tails 0.000

And I enable persistence 0.000

And I log in to a new session 0.000

And all notifications have disappeared 0.000

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:326 7.086

Output 1

SCENARIO FAILED: 'Persistent browser bookmarks' (at time 04:29:21)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:29:21_Persistent_browser_bookmarks.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:29:21_Persistent_browser_bookmarks.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:29:21_Persistent_browser_bookmarks.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:29:21_Persistent_browser_bookmarks.journal

After features/support/hooks.rb:100 0.000

Feature: Cloning a Git repository

Tags: @product @check_tor_leaks

5.887

Scenario Cloning a Git repository anonymously over HTTPS

Steps

When I clone the Git repository "https://github.com/intrigeri/Dist-Zilla-Plugin-LocaleMsgfmt.git" in GNOME Terminal 5.688

Then the Git repository "Dist-Zilla-Plugin-LocaleMsgfmt" has been cloned successfully 0.198

Hooks

After features/support/hooks.rb:515 0.373

After features/support/hooks.rb:326 0.663

After features/support/hooks.rb:100 0.000

Feature: Cloning a Git repository

Tags: @product @check_tor_leaks

8.538

Scenario Cloning git repository over SSH

Steps

Given I have the SSH key pair for a Git repository 0.248

When I clone the Git repository "ssh://gitolite3@lizard.tails.boum.org:3004/myprivatekeyispublic/testing.git" in GNOME Terminal 8.081

Then the Git repository "testing" has been cloned successfully 0.208

Hooks

After features/support/hooks.rb:515 0.606

After features/support/hooks.rb:326 1.087

After features/support/hooks.rb:100 0.000

Feature: Various checks for torified software

Tags: @product @check_tor_leaks

0.479

Scenario wget(1) should work for HTTPS and go through Tor

Steps

When I wget "https://example.com/" to stdout 0.479

Then the wget command is successful 0.000

And the wget standard output contains "Example Domain" 0.000

Hooks

After features/support/hooks.rb:515 0.264

After features/support/hooks.rb:326 0.656

After features/support/hooks.rb:100 0.000

Feature: Various checks for torified software

Tags: @product @check_tor_leaks

4.071

Scenario wget(1) with tricky options should work for HTTP and go through Tor

Steps

When I wget "some Tails mirror" to stdout with the '--spider --header="Host: dl.amnesia.boum.org"' options 4.071

Output 1

Resolved dl.amnesia.boum.org to 139.178.88.99

Resolved dl.amnesia.boum.org to 208.80.154.139

Then the wget command is successful 0.000

Hooks

After features/support/hooks.rb:515 0.782

After features/support/hooks.rb:326 0.836

After features/support/hooks.rb:100 0.000

Feature: Various checks for torified software

Tags: @product @check_tor_leaks

0.479

Scenario curl should work for HTTPS and go through Tor

Steps

When I curl "https://example.com/" to stdout 0.479

Then the curl command is successful 0.000

And the curl standard output contains "Example Domain" 0.000

Hooks

After features/support/hooks.rb:515 0.544

After features/support/hooks.rb:326 1.043

After features/support/hooks.rb:100 0.000

Feature: Using Totem

Tags: @product

51.015

Scenario Watching a MP4 video stored on the non-persistent filesystem

Steps

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

And I plug and mount a USB drive containing sample videos 15.725

And I copy the sample videos to "/home/amnesia" as user "amnesia" 0.229

And the file "/home/amnesia/video.mp4" exists 0.072

Given I start monitoring the AppArmor log of "/usr/bin/totem" 0.176

When I open "/home/amnesia/video.mp4" with Totem 3.387

Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 6.616

And AppArmor has not denied "/usr/bin/totem" from opening "/home/amnesia/video.mp4" 0.096

Given I close Totem 0.210

And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.062

And the file "/home/amnesia/.gnupg/video.mp4" exists 0.069

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.151

When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 2.213

Then Totem tells me it is not allowed to open this file 2.038

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.075

Given I close Totem 0.156

And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.060

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.150

When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 2.221

Then Totem tells me it is not allowed to open this file 1.024

And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.073

Given I close Totem 0.151

And the file "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" exists 0.039

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.138

When I try to open "/live/overlay/rw/home/amnesia/.gnupg/video.mp4" with Totem 2.211

Then Totem tells me it is not allowed to open this file 0.892

# Due to our AppArmor aliases, /live/overlay will be treated

# as /usr/lib/live/mount/overlay.

And AppArmor has denied "/usr/bin/totem" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/video.mp4" 0.102

Given I close Totem 0.157

And I copy "/home/amnesia/video.mp4" to "/home/amnesia/.purple/otr.private_key" as user "amnesia" 0.075

And the file "/home/amnesia/.purple/otr.private_key" exists 0.057

And I restart monitoring the AppArmor log of "/usr/bin/totem" 0.160

When I try to open "/home/amnesia/.purple/otr.private_key" with Totem 2.202

Then Totem tells me it is not allowed to open this file 0.922

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.purple/otr.private_key" 0.099

Hooks

After features/support/hooks.rb:326 0.828

After features/support/hooks.rb:100 0.000

Feature: Using Totem

Tags: @product @check_tor_leaks

25.829

Scenario Watching a WebM video over HTTPS

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.265

Then I can watch a WebM video over HTTPs 13.564

Hooks

After features/support/hooks.rb:515 0.623

After features/support/hooks.rb:326 0.997

After features/support/hooks.rb:100 0.000

Feature: Using Totem

Tags: @product

2:9.745

Scenario Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement

Steps

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

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Unlock Encryption" roleName='push button'
STDOUT:

STDERR:


./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/usb.rb:685: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/usb.rb:684:in `block in <top (required)>'
./features/step_definitions/usb.rb:708:in `block in <top (required)>'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `block (2 levels) 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/usb.rb:684:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:708:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/totem.feature:55:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'

And I plug and mount a USB drive containing sample videos 0.000

And I copy the sample videos to "/home/amnesia/Persistent" as user "amnesia" 0.000

When I open "/home/amnesia/Persistent/video.mp4" with Totem 0.000

Then I see "SampleLocalMp4VideoFrame.png" after at most 40 seconds 0.000

Given I close Totem 0.000

And I start monitoring the AppArmor log of "/usr/bin/totem" 0.000

And I copy the sample videos to "/home/amnesia/.gnupg" as user "amnesia" 0.000

When I try to open "/home/amnesia/.gnupg/video.mp4" with Totem 0.000

Then Totem tells me it is not allowed to open this file 0.000

And AppArmor has denied "/usr/bin/totem" from opening "/home/amnesia/.gnupg/video.mp4" 0.000

Hooks

After features/support/hooks.rb:326 7.344

Output 1

SCENARIO FAILED: 'Watching MP4 videos stored on the persistent volume should work as expected given our AppArmor confinement' (at time 04:34:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:34:32_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:34:32_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:34:32_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/3/artifact/build-artifacts/04:34:32_Watching_MP4_videos_stored_on_the_persistent_volume_should_work_as_expected_given_our_AppArmor_confinement.journal

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product

49.631

Scenario The Unsafe Browser can be disabled

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 11.656

And I disable the Unsafe Browser 3.624

And I log in to a new session 24.420

And the network is plugged 0.043

And all notifications have disappeared 6.806

When I try to start the Unsafe Browser 0.282

Then the Unsafe Browser complains that it is disabled 2.797

Hooks

After features/support/hooks.rb:326 1.066

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product

44.782

Scenario The Unsafe Browser can access the LAN

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 14.401

And a web server is running on the LAN 1.042

When I successfully start the Unsafe Browser 19.077

And I open a page on the LAN web server in the Unsafe Browser 9.982

Then the Unsafe Browser displays the LAN web server hello message 0.277

Hooks

After features/support/hooks.rb:326 0.948

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product @doc

52.939

Scenario Starting the Unsafe Browser works as it should

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.475

When I successfully start the Unsafe Browser 19.175

Then the Unsafe Browser runs as the expected user 0.711

And the Unsafe Browser has a red theme 0.582

And the Unsafe Browser shows a warning as its start page 0.631

And the Unsafe Browser has no add-ons installed 8.783

And the Unsafe Browser has no bookmarks 8.252

And the Unsafe Browser uses all expected TBB shared libraries 1.328

Hooks

After features/support/hooks.rb:326 0.846

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product

41.963

Scenario The Unsafe Browser can load a web page from the Internet

Hooks

Before features/support/hooks.rb:269 0.007

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.184

When I successfully start the Unsafe Browser 18.198

When I open the Tails homepage in the Unsafe Browser 8.552

Then the Tails homepage loads in the Unsafe Browser 1.879

And the Unsafe Browser has sent packets out to the Internet 0.148

Hooks

After features/support/hooks.rb:326 2.200

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product @not_release_blocker

34.836

Scenario Closing the Unsafe Browser shows a stop notification and properly tears down the chroot

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.423

When I successfully start the Unsafe Browser 20.172

And I close the Unsafe Browser 0.121

Then I see the "Shutting down the Unsafe Browser..." notification after at most 60 seconds 1.592

And the Unsafe Browser chroot is torn down 0.526

Hooks

After features/support/hooks.rb:326 0.742

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product @not_release_blocker

45.177

Scenario Starting a second instance of the Unsafe Browser results in an error message being shown

Hooks

Before features/support/hooks.rb:269 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.263

When I successfully start the Unsafe Browser 18.938

# Wait for whatever facility the GNOME Activities Overview uses to

# learn about which applications are running to "settle". Without

# this sleep, it is confused and it's impossible to start a new

# instance (it will just switch to the one we already started).

And I wait 10 seconds 10.010

Output 1

Slept for 10 seconds

And I try to start the Unsafe Browser 0.168

Then I see a warning about another instance already running 3.796

Hooks

After features/support/hooks.rb:326 1.158

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product

44.022

Scenario The Unsafe Browser is not allowed to use a local proxy

Hooks

Before features/support/hooks.rb:269 0.009

Steps

Given I have started Tails from DVD and logged in and the network is connected 12.756

When I configure the Unsafe Browser to use a local proxy 0.217

And I successfully start the Unsafe Browser 18.810

And I open the Tails homepage in the Unsafe Browser 11.693

Then I see "BrowserProxyRefused.png" after at most 60 seconds 0.544

Hooks

After features/support/hooks.rb:326 5.678

After features/support/hooks.rb:100 0.000

Feature: Browsing the web using the Unsafe Browser

Tags: @product @not_release_blocker @check_tor_leaks

2:36.038

Scenario The Unsafe Browser only makes user-initiated non-Torified connections

Hooks

Before features/support/hooks.rb:269 0.007

Before features/support/hooks.rb:507 0.005

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.906

And I capture all network traffic 0.007

And I configure the Unsafe Browser to check for updates more frequently 0.088

But checking for updates is disabled in the Unsafe Browser's configuration 0.019

When I successfully start the Unsafe Browser 21.350

And I wait 120 seconds 2:0.095

Output 1

Slept for 120 seconds

Then the Unsafe Browser has not sent packets out to the Internet 0.571

Hooks

After features/support/hooks.rb:515 0.603

After features/support/hooks.rb:326 0.809

After features/support/hooks.rb:100 0.042

Feature: Browsing the web using the Unsafe Browser

Tags: @product @not_release_blocker

32.937

Scenario The Unsafe Browser cannot be started when I am offline

Hooks

Before features/support/hooks.rb:269 0.006

Steps

Given I have started Tails from DVD and logged in and the network is connected 13.942

And the network is unplugged 0.076

# NetworkManager apparently needs some time to notice that the connection is now off

And I wait 10 seconds 10.025

Output 1

Slept for 10 seconds

When I try to start the Unsafe Browser 0.137

Then I am told I cannot start the Unsafe Browser when I am offline 8.755

Hooks

After features/support/hooks.rb:326 0.788

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

21.750

Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume

Steps

When I plug a USB drive containing a basic VeraCrypt volume 8.426

And I cancel the GNOME authentication prompt 1.614

And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.000

And I open this VeraCrypt volume in GNOME Files 5.267

Then I see the expected contents in this VeraCrypt volume 0.534

When I lock the currently opened VeraCrypt volume 0.728

Then the VeraCrypt volume has been unmounted and locked 0.178

Hooks

After features/support/hooks.rb:326 1.338

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

24.884

Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume

Steps

When I plug a USB drive containing a hidden VeraCrypt volume 10.523

And I cancel the GNOME authentication prompt 2.126

And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.152

And I open this VeraCrypt volume in GNOME Files 5.785

Then I see the expected contents in this VeraCrypt volume 0.407

When I lock the currently opened VeraCrypt volume 0.735

Then the VeraCrypt volume has been unmounted and locked 0.153

Hooks

After features/support/hooks.rb:326 0.810

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

35.073

Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 17.801

And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 9.054

And I open this VeraCrypt volume in GNOME Files 6.149

Then I see the expected contents in this VeraCrypt volume 1.366

When I lock the currently opened VeraCrypt file container 0.373

Then the VeraCrypt file container has been unmounted and locked 0.326

Hooks

After features/support/hooks.rb:326 0.838

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

45.570

Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container

Steps

When I plug and mount a USB drive containing a hidden VeraCrypt file container 26.349

And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 11.963

And I open this VeraCrypt volume in GNOME Files 5.793

Then I see the expected contents in this VeraCrypt volume 0.937

When I lock the currently opened VeraCrypt file container 0.374

Then the VeraCrypt file container has been unmounted and locked 0.151

Hooks

After features/support/hooks.rb:326 0.891

After features/support/hooks.rb:100 0.016

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

29.034

Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile

Steps

When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 6.982

And I cancel the GNOME authentication prompt 2.136

And I unlock and mount this VeraCrypt volume with GNOME Disks 11.162

And I open this VeraCrypt volume in GNOME Files 6.913

Then I see the expected contents in this VeraCrypt volume 0.455

When I lock the currently opened VeraCrypt volume 1.176

Then the VeraCrypt volume has been unmounted and locked 0.207

Hooks

After features/support/hooks.rb:326 2.778

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

27.574

Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume

Steps

When I plug a USB drive containing a hidden VeraCrypt volume 10.185

And I cancel the GNOME authentication prompt 2.220

And I unlock and mount this VeraCrypt volume with GNOME Disks 8.869

And I open this VeraCrypt volume in GNOME Files 5.007

Then I see the expected contents in this VeraCrypt volume 0.532

When I lock the currently opened VeraCrypt volume 0.479

Then the VeraCrypt volume has been unmounted and locked 0.279

Hooks

After features/support/hooks.rb:326 2.785

After features/support/hooks.rb:100 0.000

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

53.074

Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 23.849

And I unlock and mount this VeraCrypt file container with GNOME Disks 22.457

And I open this VeraCrypt volume in GNOME Files 5.119

Then I see the expected contents in this VeraCrypt volume 0.823

When I lock the currently opened VeraCrypt file container 0.531

Then the VeraCrypt file container has been unmounted and locked 0.292

Hooks

After features/support/hooks.rb:326 1.670

After features/support/hooks.rb:100 0.015

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

52.532

Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container

Steps

When I plug and mount a USB drive containing a hidden VeraCrypt file container 25.960

And I unlock and mount this VeraCrypt file container with GNOME Disks 19.959

And I open this VeraCrypt volume in GNOME Files 4.990

Then I see the expected contents in this VeraCrypt volume 0.912

When I lock the currently opened VeraCrypt file container 0.536

Then the VeraCrypt file container has been unmounted and locked 0.173

Hooks

After features/support/hooks.rb:326 0.900

After features/support/hooks.rb:100 0.016

Feature: Using VeraCrypt encrypted volumes

Tags: @product @not_release_blocker

42.341

Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM

Steps

When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 15.936

And I unlock and mount this VeraCrypt file container with GNOME Disks 19.403

And I open this VeraCrypt volume in GNOME Files 5.061

Then I see the expected contents in this VeraCrypt volume 1.224

When I lock the currently opened VeraCrypt file container 0.474

Then the VeraCrypt file container has been unmounted and locked 0.240

Hooks

After features/support/hooks.rb:326 0.849

After features/support/hooks.rb:100 0.000

Feature: I can report a bug with WhisperBack

Tags: @product

9.191

Scenario The amnesia user cannot run tails-debugging-info as root

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

Then running "sudo /usr/local/sbin/tails-debugging-info" as user "amnesia" fails 0.116

Hooks

After features/support/hooks.rb:326 1.389

After features/support/hooks.rb:100 0.000

Feature: I can report a bug with WhisperBack

Tags: @product

10.820

Scenario All debugging information can be retrieved

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

Then running "/usr/local/sbin/tails-debugging-info --strict" as user "root" succeeds 1.112

Hooks

After features/support/hooks.rb:326 0.805

After features/support/hooks.rb:100 0.000

Feature: I can report a bug with WhisperBack

Tags: @product

23.207

Scenario WhisperBack has access to debugging information

Hooks

Before features/support/hooks.rb:269 0.006

Steps

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

When I start "WhisperBack" via GNOME Activities Overview 10.028

Then WhisperBack has debugging information 4.542

Hooks

After features/support/hooks.rb:326 1.169

After features/support/hooks.rb:100 0.000

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@product	1161	38	323	0	0	1522	166	40	206	4:23:48.898	Failed

Tag Report