Project Number Date
test_Tails_ISO_stable 5717 16 Jun 2025, 16:25

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 37:30.197 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:16.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.245
Given a computer 1.188
And I create a 7200 MiB disk named "old" 0.119
And I plug USB drive "old" 1.205
And I write an old version of the Tails USB image to disk "old" 1:26.836
When I start Tails from USB drive "old" with network unplugged 2:41.467
Then the boot device has safe access rights 4.393
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 9.462
After features/support/hooks.rb:100 0.027
Tags: @product
4:23.063
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given a computer 0.671
And I start Tails from USB drive "old" with network unplugged and I login 2:48.678
Then Tails is running from USB drive "old" 0.807
And I create a persistent partition 1:12.358
And I take note of which tps features are available 3.003
Then a Tails persistence partition exists on USB drive "old" 0.937
And I shutdown Tails and wait for the computer to power off 16.606
After features/support/hooks.rb:330 0.262
After features/support/hooks.rb:100 0.028
Tags: @product
7:0.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.375
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 5:9.194
Then Tails is running from USB drive "old" 10.133
And all tps features are active 3.444
When I write some files expected to persist 2.882
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.533
And all persistent directories from the old Tails version have safe access rights 13.660
And I take note of which tps features are available 1.043
And I shutdown Tails and wait for the computer to power off 6.632
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:12.605
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.016
Tags: @product
1:58.096
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.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 36.719
And I log in to a new session 43.580
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.426
And I plug USB drive "to_upgrade" 2.770
When I upgrade Tails to USB drive "to_upgrade" by cloning 32.599
cannot 
cannot find TailsClonerWindow.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/usb.rb:156: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 5.698 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 02:23:32)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5717/artifact/build-artifacts/02:23:32_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5717/artifact/build-artifacts/02:23:32_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5717/artifact/build-artifacts/02:23:32_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5717/artifact/build-artifacts/02:23:32_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
4:34.349
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.258
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:2.839
Then all tps features from the old Tails version are active 10.542
And Tails is running from USB drive "to_upgrade" 0.813
And the boot device has safe access rights 4.254
And the expected persistent files created with the old Tails version are present in the filesystem 2.418
And all persistent directories from the old Tails version have safe access rights 13.223
After features/support/hooks.rb:330 1.658
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
13:23.602
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 26.020
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.420
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.159
And the file system changes introduced in version 6.2~testoverlayfs are not present 4.455
And the file system changes introduced in version 6.3~testoverlayfs are not present 5.371
When the network is plugged 0.464
And Tor is ready 45.818
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 16.681
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 38.936
Given I shutdown Tails and wait for the computer to power off 20.853
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:49.743
Then Tails is running version 6.2~testoverlayfs 1.519
And all tps features are active 8.499
And the file system changes introduced in version 6.2~testoverlayfs are present 0.445
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.352
When the network is plugged 0.508
And Tor is ready 39.422
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 17.987
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 20.926
Given I shutdown Tails and wait for the computer to power off 6.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:59.199
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 6.938
And the file system changes introduced in version 6.3~testoverlayfs are present 3.960
And only the 6.3~testoverlayfs SquashFS delta is installed 0.900
# 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.824
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.778
When the network is plugged 0.145
And Tor is ready 31.269
Then the Upgrader considers the system as up-to-date 0.810
# 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 30.839
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.206
After features/support/hooks.rb:330 1.180
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
1:53.974
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 43.729
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.723
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.474
And the signing key used by the Upgrader is outdated 1.588
But a current signing key is available on our website 0.000
When the network is plugged 0.710
And Tor is ready 47.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 16.550
After features/support/hooks.rb:330 1.405
After features/support/hooks.rb:100 0.000