Project Number Date
test_Tails_ISO_21548-flatpak-install 16 22 May 2026, 18:09

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 9:11.509 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
1:23.844
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.214
When I start Tails from USB drive "old" with network unplugged 1:4.625
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 3.720
After features/support/hooks.rb:104 0.006
Tags: @product
1:34.491
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 59.055
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 26.860
And I take note of which tps features are available 0.354
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 7.140
After features/support/hooks.rb:335 0.455
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.282
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.512
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.167
When I write some files expected to persist 1.383
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.012
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.289
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.937
After features/support/hooks.rb:335 0.666
After features/support/hooks.rb:104 0.037
Tags: @product
2:14.782
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.023
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.869
And I log in to a new session 13.952
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.988
And I plug USB drive "to_upgrade" 2.272
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.861
Then the running Tails is installed on USB drive "to_upgrade" 16.543
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.048
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.363
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.025
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.378
Then all tps features from the old Tails version are active 1.359
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 3.029
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 2.079
After features/support/hooks.rb:335 0.878
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
38.112
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 38.112
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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:335 4.912 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:02:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:03_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_21548-flatpak-install/16/artifact/build-artifacts/01:02:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:03_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:104 0.000
Tags: @product @automatic_upgrade
34.631
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 34.631
Feature 
Feature 'Flatpak' is not active.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:793:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:788:in `each'
./features/step_definitions/usb.rb:788:in `/^all tps features(| from the old Tails version)(| but the first one) are active$/'
./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:335 4.782 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:02:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:43_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:43_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:43_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21548-flatpak-install/16/artifact/build-artifacts/01:02:43_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:104 0.000