Project Number Date
test_Tails_ISO_20904-tor-browser-14.5-force-all-tests 1 22 Apr 2025, 21:43

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 85 1 1 0 0 87 6 1 7 21:29.260 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:41.360
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 1.172
And I create a 7200 MiB disk named "old" 0.093
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 1:7.068
When I start Tails from USB drive "old" with network unplugged 1:27.447
Then the boot device has safe access rights 3.348
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.133
And udev-watchdog is monitoring the correct device 0.344
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 6.983
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.224
And I start Tails from USB drive "old" with network unplugged and I login 1:25.918
Then Tails is running from USB drive "old" 0.410
And I create a persistent partition 32.429
And I take note of which tps features are available 2.410
Then a Tails persistence partition exists on USB drive "old" 0.940
And I shutdown Tails and wait for the computer to power off 8.691
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.009
Tags: @product
2:53.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.375
Then Tails is running from USB drive "old" 0.445
And all tps features are active 2.075
When I write some files expected to persist 1.760
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 3.533
And I take note of which tps features are available 0.576
And I shutdown Tails and wait for the computer to power off 6.582
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.720
After features/support/hooks.rb:330 0.166
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.097
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.957
And I log in to a new session 22.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.806
And I plug USB drive "to_upgrade" 2.616
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.847
Then the running Tails is installed on USB drive "to_upgrade" 28.105
And I unplug USB drive "to_upgrade" 0.260
And I unplug USB drive "__internal" 0.263
After features/support/hooks.rb:330 1.430
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.067
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.191
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.481
Then all tps features from the old Tails version are active 1.724
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.518
And the expected persistent files created with the old Tails version are present in the filesystem 2.021
And all persistent directories from the old Tails version have safe access rights 2.779
After features/support/hooks.rb:330 1.659
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:59.291
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.556
And no SquashFS delta is installed 0.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.329
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.073
And Tor is ready 27.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.764
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.925
Given I shutdown Tails and wait for the computer to power off 11.054
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.736
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.798
And the file system changes introduced in version 6.2~testoverlayfs are present 0.397
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.419
# 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.341
When the network is plugged 0.089
And Tor is ready 19.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.781
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.393
Given I shutdown Tails and wait for the computer to power off 6.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.948
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.295
And the file system changes introduced in version 6.3~testoverlayfs are present 0.613
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.310
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.370
When the network is plugged 0.096
And Tor is ready 18.426
Then the Upgrader considers the system as up-to-date 11.017
# 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 1:0.110
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "Firefox" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1046:in `new'
./features/step_definitions/common_steps.rb:1046:in `block in launch_app'
./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/common_steps.rb:1045:in `launch_app'
./features/step_definitions/common_steps.rb:1117:in `launch_unsafe_browser'
./features/step_definitions/browser.rb:69:in `block in <top (required)>'
./features/step_definitions/browser.rb:73: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/common_steps.rb:1045:in `launch_app'
./features/step_definitions/common_steps.rb:1117:in `launch_unsafe_browser'
./features/step_definitions/browser.rb:69:in `/^I (try to )?start the Unsafe Browser$/'
./features/step_definitions/browser.rb:73:in `/^I successfully start the Unsafe Browser(?: in "([^"]+)")?$/'
features/usb_upgrade.feature:122:in `And I successfully start the Unsafe Browser'
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:330 8.148 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:57:16)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20904-tor-browser-14.5-force-all-tests/1/artifact/build-artifacts/01:57:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20904-tor-browser-14.5-force-all-tests/1/artifact/build-artifacts/01:57:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20904-tor-browser-14.5-force-all-tests/1/artifact/build-artifacts/01:57:16_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
40.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.271
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.375
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 18.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.824
After features/support/hooks.rb:330 0.677
After features/support/hooks.rb:100 0.000