Project Number Date
test_Tails_ISO_stable 6693 26 Sep 2026, 12:16

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:4.716 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
55.260
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.858
When I start Tails from USB drive "old" with network unplugged 38.891
Then the boot device has safe access rights 1.780
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.750
After features/support/hooks.rb:108 0.005
Tags: @product
37.116
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.001
Steps
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 37.041
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 4.778 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:38:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_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_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:38:38_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.005
Tags: @product
45.103
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.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 45.010
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 4.819 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:39:28)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:39:28_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_stable/6693/artifact/build-artifacts/01:39:28_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_stable/6693/artifact/build-artifacts/01:39:28_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_stable/6693/artifact/build-artifacts/01:39:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.742
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.922
And I log in to a new session 11.831
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.515
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.860
Then the running Tails is installed on USB drive "to_upgrade" 17.137
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.781
After features/support/hooks.rb:108 0.000
Tags: @product
47.235
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.002
Steps
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 47.162
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.176 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:42:33)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_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_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6693/artifact/build-artifacts/01:42:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:32.178
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.060
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.307
When the network is plugged 0.026
And Tor is ready 12.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.415
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.382
Given I shutdown Tails and wait for the computer to power off 5.175
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.438
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.503
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.174
When the network is plugged 0.037
And Tor is ready 10.108
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.901
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.495
Given I shutdown Tails and wait for the computer to power off 2.666
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.823
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.329
And the file system changes introduced in version 6.3~testoverlayfs are present 0.258
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.148
When the network is plugged 0.034
And Tor is ready 10.164
Then the Upgrader considers the system as up-to-date 0.091
# 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.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.036
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.931
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000