Project Number Date
test_Tails_ISO_stable 4765 03 Apr 2024, 17:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails persistence
Tags: @product
1:9.707
Scenario Writing files to a read/write-enabled persistent partition
Before features/support/hooks.rb:245 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.651
And the network is plugged 0.053
And Tor is ready 1:0.002
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:625:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:601:in `/^Tor is ready$/'
features/persistence.feature:75:in `And Tor is ready'
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
After features/support/hooks.rb:291 9.683 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition' (at time 02:59:02)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4765/artifact/build-artifacts/02:59:02_Writing_files_to_a_read_write-enabled_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4765/artifact/build-artifacts/02:59:02_Writing_files_to_a_read_write-enabled_persistent_partition.mkv
After features/support/hooks.rb:75 0.000