Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 1 16 Jun 2025, 17:44

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 48 2 37 0 0 87 5 2 7 25:6.660 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:33.523
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 1:16.900
When I start Tails from USB drive "old" with network unplugged 3:0.619
Then the boot device has safe access rights 10.561
And Tails is running from USB drive "old" 2.504
And there is no persistence partition on USB drive "old" 0.342
And process "udev-watchdog" is running 0.260
And udev-watchdog is monitoring the correct device 0.743
And I unplug USB drive "old" 0.291
After features/support/hooks.rb:330 4.322
After features/support/hooks.rb:100 0.035
Tags: @product
4:51.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.032
Given a computer 0.971
And I start Tails from USB drive "old" with network unplugged and I login 3:4.567
Then Tails is running from USB drive "old" 6.547
And I create a persistent partition 1:21.635
And I take note of which tps features are available 3.857
Then a Tails persistence partition exists on USB drive "old" 1.207
And I shutdown Tails and wait for the computer to power off 12.620
After features/support/hooks.rb:330 1.837
After features/support/hooks.rb:100 0.063
Tags: @product
6:2.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.089
Given a computer 0.614
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:24.550
Then Tails is running from USB drive "old" 1.290
And all tps features are active 5.779
When I write some files expected to persist 10.701
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.279
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 3.955
And I take note of which tps features are available 0.635
And I shutdown Tails and wait for the computer to power off 15.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 59.594
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.013
Tags: @product
1:38.829
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 25.524
And I log in to a new session 37.626
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.004
And I plug USB drive "to_upgrade" 3.598
When I upgrade Tails to USB drive "to_upgrade" by cloning 29.076
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 6.732 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 03:04:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:04:16_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_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:04:16_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:04:16_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:04:16_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:100 0.000
Tags: @product
4:54.237
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.304
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:23.035
Then all tps features from the old Tails version are active 9.831
And Tails is running from USB drive "to_upgrade" 0.543
And the boot device has safe access rights 4.915
And the expected persistent files created with the old Tails version are present in the filesystem 3.101
And all persistent directories from the old Tails version have safe access rights 12.505
After features/support/hooks.rb:330 4.873
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
1:28.827
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:28.827
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:330 7.057 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:10:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:10:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:10:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:10:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/1/artifact/build-artifacts/03:10:53_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
1:36.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 5.753
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.176
And the signing key used by the Upgrader is outdated 0.169
But a current signing key is available on our website 0.000
When the network is plugged 0.235
And Tor is ready 1:5.482
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.876
After features/support/hooks.rb:330 1.030
After features/support/hooks.rb:100 0.000