Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 2 25 Oct 2024, 18:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 44 2 41 0 0 87 5 2 7 14:23.658 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:16.451
Before features/support/hooks.rb:269 0.005
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 36.049
When I start Tails from USB drive "old" with network unplugged 1:34.707
Then the boot device has safe access rights 3.238
And Tails is running from USB drive "old" 0.344
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.135
And udev-watchdog is monitoring the correct device 0.392
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:326 7.909
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.955
Before features/support/hooks.rb:269 0.006
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login 1:27.514
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 31.892
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.854
And I shutdown Tails and wait for the computer to power off 8.796
After features/support/hooks.rb:326 0.253
After features/support/hooks.rb:100 0.009
Tags: @product
3:21.643
Before features/support/hooks.rb:269 0.006
Given a computer 1.111
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:30.767
Then Tails is running from USB drive "old" 1.075
And all tps features are active 4.224
When I write some files expected to persist 1.873
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.931
And all persistent directories from the old Tails version have safe access rights 2.677
And I take note of which tps features are available 3.555
And I shutdown Tails and wait for the computer to power off 7.227
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.954
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
2:50.120
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.207
And I log in to a new session 22.348
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.289
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.486
Then the running Tails is installed on USB drive "to_upgrade" 23.586
And I unplug USB drive "to_upgrade" 0.436
And I unplug USB drive "__internal" 0.304
After features/support/hooks.rb:326 0.944
After features/support/hooks.rb:100 0.000
Tags: @product
2:23.400
Before features/support/hooks.rb:269 0.009
Given a computer 0.626
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.422
Then all tps features from the old Tails version are active 1.637
And Tails is running from USB drive "to_upgrade" 0.409
And the boot device has safe access rights 3.490
And the expected persistent files created with the old Tails version are present in the filesystem 1.953
And all persistent directories from the old Tails version have safe access rights 2.860
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
39.692
Scenario Upgrading an initial Tails installation with an incremental upgrade
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 39.692
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702: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
After features/support/hooks.rb:326 5.551 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:22:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:22:47_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_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:22:47_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:22:47_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:22:47_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
41.393
Scenario Upgrading a Tails whose signing key is outdated
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 41.393
The 
The Dogtail init script raised: SearchError: descendent of [application | Welcome to Tails!]: child with name="Your Persistent Storage is unlocked. Its content will be available until you shut down Tails." roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:695:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702: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
After features/support/hooks.rb:326 5.464 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:23:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:23:34_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:23:34_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:23:34_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20635-greeter-threading-fixes/2/artifact/build-artifacts/01:23:34_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000