Project Number Date
test_Tails_ISO_stable 4544 30 Nov 2023, 21:25

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
1:23.025
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:245 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.644
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.361
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.600
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 1:11.304
The 
The system is not fully running yet:
No jobs running.

  UNIT               LOAD   ACTIVE SUB    DESCRIPTION
● session-c194.scope loaded failed failed Session c194 of user root

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 (RuntimeError)
./features/step_definitions/common_steps.rb:642:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:637:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:605:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:556:in `/^Tor is ready$/'
features/usb_upgrade.feature:133:in `And Tor is ready'
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.000
After features/support/hooks.rb:291 4.356 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:53:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/01:53:59_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:75 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
44.135
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 7.111
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 21.535
And I open this VeraCrypt volume in GNOME Files 15.488
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "org.gnome.Nautilus" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/veracrypt.rb:304:in `new'
./features/step_definitions/veracrypt.rb:304:in `/^I open this VeraCrypt volume in GNOME Files$/'
features/veracrypt.feature:15:in `And I open this VeraCrypt volume in GNOME Files'
Then I see "SecretFileOnVeraCryptVolume.png" after at most 10 seconds 0.000
When I lock the currently opened VeraCrypt volume 0.000
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:291 4.370 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 04:23:24)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/04:23:24_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/04:23:24_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/04:23:24_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4544/artifact/build-artifacts/04:23:24_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:75 0.000