Project Number Date
test_Tails_ISO_stable 5757 03 Jul 2025, 14:43

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 64 4 19 0 0 87 3 4 7 26:48.677 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
4:1.747
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.201
Steps
Given a computer 0.940
And I create a 7200 MiB disk named "old" 0.106
And I plug USB drive "old" 1.277
And I write an old version of the Tails USB image to disk "old" 1:3.928
When I start Tails from USB drive "old" with network unplugged 2:37.343
Then the boot device has safe access rights 5.186
And Tails is running from USB drive "old" 1.188
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.366
And I unplug USB drive "old" 11.187
Call 
Call to virDomainDetachDeviceFlags failed: Unable to read from monitor: Connection reset by peer (Guestfs::Error)
./features/support/helpers/vm_helper.rb:367:in `detach_device'
./features/support/helpers/vm_helper.rb:367:in `unplug_drive'
./features/step_definitions/usb.rb:121:in `/^I unplug USB drive "([^"]+)"$/'
features/usb_upgrade.feature:31:in `And I unplug USB drive "old"'
After features/support/hooks.rb:330 4.415 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:47:45)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:47:45_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:47:45_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:47:45_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.012
Tags: @product
2:37.470
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Steps
Given a computer 0.271
And I start Tails from USB drive "old" with network unplugged and I login 2:37.199
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./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:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:330 5.678 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:50:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:50:27_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:50:27_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:50:27_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:50:27_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.029
Tags: @product
2:55.774
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Steps
Given a computer 0.237
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:55.536
The 
The Dogtail init script raised: SearchError: descendent 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:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 5.177 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:53:28)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:53: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.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:53:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:53:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/02:53:28_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.050
Tags: @product
4:52.274
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 48.223
And I log in to a new session 39.513
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.279
And I plug USB drive "to_upgrade" 2.805
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:17.856
Then the running Tails is installed on USB drive "to_upgrade" 47.839
And I unplug USB drive "to_upgrade" 6.954
And I unplug USB drive "__internal" 2.801
After features/support/hooks.rb:330 3.969
After features/support/hooks.rb:100 0.000
Tags: @product
2:22.811
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given a computer 0.392
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:22.418
The 
The Dogtail init script raised: SearchError: descendent 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:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291: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:330 10.986 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 03:00:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/03:00:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/03:00:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/03:00:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5757/artifact/build-artifacts/03:00:56_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.288
Tags: @product @automatic_upgrade
8:50.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.123
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.863
And no SquashFS delta is installed 0.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.562
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.480
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.633
When the network is plugged 0.077
And Tor is ready 33.167
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.153
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.459
Given I shutdown Tails and wait for the computer to power off 15.771
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.943
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.999
And the file system changes introduced in version 6.2~testoverlayfs are present 0.372
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.318
When the network is plugged 0.075
And Tor is ready 21.684
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 12.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.298
Given I shutdown Tails and wait for the computer to power off 8.710
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.491
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 3.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.676
And only the 6.3~testoverlayfs SquashFS delta is installed 0.127
# 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.458
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.305
When the network is plugged 0.065
And Tor is ready 19.374
Then the Upgrader considers the system as up-to-date 0.332
# 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 20.938
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.714
After features/support/hooks.rb:330 4.995
After features/support/hooks.rb:100 0.109
Tags: @product @automatic_upgrade
1:7.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.034
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.730
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.090
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 54.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.630
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.000