Project Number Date
test_Tails_ISO_feature-arti 98 26 Jun 2025, 18:32

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 83 1 3 0 0 87 6 1 7 21:3.427 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:29.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.235
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 36.414
When I start Tails from USB drive "old" with network unplugged 1:44.124
Then the boot device has safe access rights 4.752
And Tails is running from USB drive "old" 1.523
And there is no persistence partition on USB drive "old" 0.280
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.444
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:330 3.971
After features/support/hooks.rb:100 0.008
Tags: @product
2:28.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 1:38.183
Then Tails is running from USB drive "old" 0.554
And I create a persistent partition 36.363
And I take note of which tps features are available 2.303
Then a Tails persistence partition exists on USB drive "old" 1.138
And I shutdown Tails and wait for the computer to power off 9.663
After features/support/hooks.rb:330 0.198
After features/support/hooks.rb:100 0.008
Tags: @product
3:33.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:38.824
Then Tails is running from USB drive "old" 1.042
And all tps features are active 4.188
When I write some files expected to persist 3.982
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.571
And all persistent directories from the old Tails version have safe access rights 3.177
And I take note of which tps features are available 0.569
And I shutdown Tails and wait for the computer to power off 6.279
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 34.485
After features/support/hooks.rb:330 0.188
After features/support/hooks.rb:100 0.040
Tags: @product
1:11.701
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.018
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.491
And I log in to a new session 26.374
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.010
And I plug USB drive "to_upgrade" 2.616
When I upgrade Tails to USB drive "to_upgrade" by cloning 30.208
try_for() 
try_for() timeout expired (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:1057:in `launch_app'
./features/step_definitions/common_steps.rb:1072:in `launch_gnome_terminal'
./features/step_definitions/common_steps.rb:949:in `/^I run "([^"]+)" in GNOME Terminal$/'
./features/step_definitions/usb.rb:147:in `/^I start Tails Installer$/'
./features/step_definitions/usb.rb:187:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_upgrade.feature:65:in `When I upgrade Tails to USB drive "to_upgrade" by cloning'
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 11.190 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:38:48)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/98/artifact/build-artifacts/02:38:48_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/98/artifact/build-artifacts/02:38:48_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/98/artifact/build-artifacts/02:38:48_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
2:55.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:41.722
Then all tps features from the old Tails version are active 2.102
And Tails is running from USB drive "to_upgrade" 0.417
And the boot device has safe access rights 6.402
And the expected persistent files created with the old Tails version are present in the filesystem 1.715
And all persistent directories from the old Tails version have safe access rights 3.153
After features/support/hooks.rb:330 1.601
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
7:43.109
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.752
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.636
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.221
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.087
And Tor is ready 21.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.800
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.654
Given I shutdown Tails and wait for the computer to power off 10.635
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.645
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.267
And the file system changes introduced in version 6.2~testoverlayfs are present 0.535
And only the 6.2~testoverlayfs SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.344
# 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.438
When the network is plugged 0.065
And Tor is ready 21.415
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.335
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.465
Given I shutdown Tails and wait for the computer to power off 8.442
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:23.996
Then Tails is running version 6.3~testoverlayfs 0.093
And all tps features are active 2.886
And the file system changes introduced in version 6.3~testoverlayfs are present 0.735
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.568
When the network is plugged 0.071
And Tor is ready 22.284
Then the Upgrader considers the system as up-to-date 0.343
# 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.482
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.336
After features/support/hooks.rb:330 0.718
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
41.608
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.879
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.491
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.409
And the signing key used by the Upgrader is outdated 0.236
But a current signing key is available on our website 0.000
When the network is plugged 0.264
And Tor is ready 20.169
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.158
After features/support/hooks.rb:330 1.514
After features/support/hooks.rb:100 0.000