Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 11 06 Apr 2026, 02:34

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 74 2 11 0 0 87 5 2 7 11:59.325 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:46.321
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.458
When I start Tails from USB drive "old" with network unplugged 1:28.680
Then the boot device has safe access rights 2.459
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.172
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.389
After features/support/hooks.rb:100 0.078
Tags: @product
1:26.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 57.214
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 23.584
And I take note of which tps features are available 0.787
Then a Tails persistence partition exists on USB drive "old" 0.587
And I shutdown Tails and wait for the computer to power off 4.473
After features/support/hooks.rb:331 0.397
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.482
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.884
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.127
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 4.058
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.178
After features/support/hooks.rb:331 0.353
After features/support/hooks.rb:100 0.005
Tags: @product
1:37.180
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.928
And I log in to a new session 1:29.252
Known 
Known issue #21211: timed out while waiting for the GNOME Shell Introspect API (RuntimeError)
./features/step_definitions/common_steps.rb:399:in `rescue in wait_for_ponytail'
./features/step_definitions/common_steps.rb:388:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:622:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:538:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/usb_upgrade.feature:62:in `And I log in to a new session'
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.000
And I plug USB drive "to_upgrade" 0.000
When I upgrade Tails to USB drive "to_upgrade" by cloning 0.000
Then the running Tails is installed on USB drive "to_upgrade" 0.000
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:331 10.582 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:06:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21472-circumvention-settings-2/11/artifact/build-artifacts/01:06:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21472-circumvention-settings-2/11/artifact/build-artifacts/01:06:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21472-circumvention-settings-2/11/artifact/build-artifacts/01:06:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
0.057
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.001
Steps
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.010
Call 
Call to virStorageVolLookupByName failed: Storage volume not found: no storage vol with matching name 'to_upgrade' (Libvirt::RetrieveError)
./features/support/helpers/storage_helper.rb:151:in `lookup_volume_by_name'
./features/support/helpers/storage_helper.rb:151:in `disk_path'
./features/support/helpers/vm_helper.rb:337:in `plug_drive'
./features/support/helpers/vm_helper.rb:416:in `set_disk_boot'
./features/step_definitions/common_steps.rb:108:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:233: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
Hooks
After features/support/hooks.rb:331 4.395
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:465:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:460:in `each'
./features/support/hooks.rb:460:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:07:10)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21472-circumvention-settings-2/11/artifact/build-artifacts/01:07:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21472-circumvention-settings-2/11/artifact/build-artifacts/01:07:10_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
5:0.849
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 with a persistent partition enabled and logged in 9.240
And no SquashFS delta is installed 0.266
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.751
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.356
When the network is plugged 0.040
And Tor is ready 38.785
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.755
Given I shutdown Tails and wait for the computer to power off 28.828
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.184
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.108
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.198
# 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.200
When the network is plugged 0.021
And Tor is ready 20.220
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.608
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.234
Given I shutdown Tails and wait for the computer to power off 18.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.182
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.050
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.018
And Tor is ready 21.158
Then the Upgrader considers the system as up-to-date 0.162
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.383
After features/support/hooks.rb:331 0.826
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
47.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.900
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 38.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.000