Project Number Date
test_Tails_ISO_stable 6290 13 Apr 2026, 17:27

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 12:51.674 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:0.531
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.215
When I start Tails from USB drive "old" with network unplugged 42.753
Then the boot device has safe access rights 2.776
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:331 3.561
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.428
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.115
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 8.360
After features/support/hooks.rb:331 0.382
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.720
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.002
Steps
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:26.672
can 
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:444:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235: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:331 5.330 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:06:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6290/artifact/build-artifacts/01:06:52_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/6290/artifact/build-artifacts/01:06:52_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/6290/artifact/build-artifacts/01:06:52_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/6290/artifact/build-artifacts/01:06:52_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.443
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.608
And I log in to a new session 17.222
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.700
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.349
Then the running Tails is installed on USB drive "to_upgrade" 16.011
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 4.129
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.269
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.003
Steps
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.631
Then all tps features from the old Tails version are active 0.959
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.355
And the expected persistent files created with the old Tails version are present in the filesystem 0.040
Could 
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1110:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1109:in `each'
./features/step_definitions/usb.rb:1109:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:331 5.052 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:10:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6290/artifact/build-artifacts/01:10:27_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/6290/artifact/build-artifacts/01:10:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6290/artifact/build-artifacts/01:10:27_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/6290/artifact/build-artifacts/01:10:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:3.625
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.300
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.015
And Tor is ready 27.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.674
Given I shutdown Tails and wait for the computer to power off 20.730
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.844
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.216
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.185
# 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.218
When the network is plugged 0.016
And Tor is ready 20.185
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.819
Given I shutdown Tails and wait for the computer to power off 18.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.704
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.017
And Tor is ready 39.494
Then the Upgrader considers the system as up-to-date 0.097
# 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 4.411
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 1.024
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.493
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 20.377
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
After features/support/hooks.rb:331 0.614
After features/support/hooks.rb:100 0.000