Project Number Date
test_Tails_ISO_feature-arti 93 18 Jun 2025, 20:47

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 24:0.450 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
2:31.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.345
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 37.461
When I start Tails from USB drive "old" with network unplugged 1:45.608
Then the boot device has safe access rights 5.099
And Tails is running from USB drive "old" 0.570
And there is no persistence partition on USB drive "old" 0.118
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.507
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:330 4.080
After features/support/hooks.rb:100 0.008
Tags: @product
2:53.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login 2:2.955
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 37.805
And I take note of which tps features are available 2.646
Then a Tails persistence partition exists on USB drive "old" 0.902
And I shutdown Tails and wait for the computer to power off 8.946
After features/support/hooks.rb:330 0.248
After features/support/hooks.rb:100 0.009
Tags: @product
4:7.085
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.253
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:6.703
Then Tails is running from USB drive "old" 0.637
And all tps features are active 2.500
When I write some files expected to persist 2.644
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.301
And all persistence configuration files have safe access rights 0.490
And all persistent directories from the old Tails version have safe access rights 5.952
And I take note of which tps features are available 0.665
And I shutdown Tails and wait for the computer to power off 6.799
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.135
After features/support/hooks.rb:330 0.146
After features/support/hooks.rb:100 0.014
Tags: @product
3:19.463
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.007
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.154
And I log in to a new session 3:6.309
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/common_steps.rb:577:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:533: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:330 9.114 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 03:19:59)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/93/artifact/build-artifacts/03:19:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/93/artifact/build-artifacts/03:19:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/93/artifact/build-artifacts/03:19:59_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
0.567
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.076
Steps
Given a computer 0.515
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 0.052
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:155:in `/^the computer is set to boot from (.+?) drive "(.+?)"$/'
./features/step_definitions/common_steps.rb:293: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:330 4.692
Error message 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/hooks.rb:455:in `block (2 levels) in <top (required)>'
./features/support/hooks.rb:450:in `each'
./features/support/hooks.rb:450:in `After'
Output 1 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 03:20:09)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/93/artifact/build-artifacts/03:20:09_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/93/artifact/build-artifacts/03:20:09_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
10:20.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.619
And no SquashFS delta is installed 0.907
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.399
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.188
When the network is plugged 0.127
And Tor is ready 25.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.934
Given I shutdown Tails and wait for the computer to power off 1:41.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.429
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.036
And the file system changes introduced in version 6.2~testoverlayfs are present 0.452
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.425
When the network is plugged 0.087
And Tor is ready 26.424
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.013
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.614
Given I shutdown Tails and wait for the computer to power off 6.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.343
Then Tails is running version 6.3~testoverlayfs 0.032
And all tps features are active 3.300
And the file system changes introduced in version 6.3~testoverlayfs are present 0.638
And only the 6.3~testoverlayfs SquashFS delta is installed 0.096
# 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.370
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.087
And Tor is ready 25.460
Then the Upgrader considers the system as up-to-date 0.355
# 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 24.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.012
After features/support/hooks.rb:330 0.974
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
48.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.429
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.874
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.182
And the signing key used by the Upgrader is outdated 0.257
But a current signing key is available on our website 0.000
When the network is plugged 0.179
And Tor is ready 24.367
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.793
After features/support/hooks.rb:330 1.489
After features/support/hooks.rb:100 0.000