Project Number Date
test_Tails_ISO_issue-template-stop-tracking-oldstable 1 01 Oct 2026, 17:35

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 65 3 19 0 0 87 4 3 7 9:48.952 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:20.817
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.894
When I start Tails from USB drive "old" with network unplugged 1:2.695
Then the boot device has safe access rights 2.400
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.720
After features/support/hooks.rb:108 0.051
Tags: @product
40.358
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Steps
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 40.278
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:339 5.012 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:13:02)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:02_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.006
Tags: @product
47.445
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 47.360
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# 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" 0.000
After features/support/hooks.rb:339 5.109 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:13:54)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:54_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:54_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:54_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:13:54_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.006
Tags: @product
2:18.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.355
And I log in to a new session 12.430
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.727
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.431
Then the running Tails is installed on USB drive "to_upgrade" 19.546
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 3.731
After features/support/hooks.rb:108 0.000
Tags: @product
48.438
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.121
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 48.316
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 5.000 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:17:10)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:17:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:17:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:17:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_issue-template-stop-tracking-oldstable/1/artifact/build-artifacts/01:17:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:32.562
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.462
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.294
When the network is plugged 0.035
And Tor is ready 12.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.066
Given I shutdown Tails and wait for the computer to power off 5.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.338
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.113
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.077
# 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.240
When the network is plugged 0.027
And Tor is ready 10.329
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.319
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.611
Given I shutdown Tails and wait for the computer to power off 3.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.330
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 7.664
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.023
And Tor is ready 10.544
Then the Upgrader considers the system as up-to-date 0.072
# 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 3.589
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.438
After features/support/hooks.rb:339 0.798
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
20.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.193
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 10.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.623
After features/support/hooks.rb:339 0.835
After features/support/hooks.rb:108 0.000