Project Number Date
test_Tails_ISO_21014-htpdateerror 29 16 Jul 2025, 02:29

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 52 1 34 0 0 87 6 1 7 27:54.365 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:34.972
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.384
And I create a 7200 MiB disk named "old" 0.320
And I plug USB drive "old" 2.618
And I write an old version of the Tails USB image to disk "old" 1:11.851
When I start Tails from USB drive "old" with network unplugged 3:5.358
Then the boot device has safe access rights 12.903
And Tails is running from USB drive "old" 0.505
And there is no persistence partition on USB drive "old" 0.141
And process "udev-watchdog" is running 0.152
And udev-watchdog is monitoring the correct device 0.415
And I unplug USB drive "old" 0.318
After features/support/hooks.rb:330 3.981
After features/support/hooks.rb:100 0.013
Tags: @product
4:49.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 3:13.764
Then Tails is running from USB drive "old" 0.830
And I create a persistent partition 1:6.360
And I take note of which tps features are available 9.346
Then a Tails persistence partition exists on USB drive "old" 2.575
And I shutdown Tails and wait for the computer to power off 16.733
After features/support/hooks.rb:330 0.922
After features/support/hooks.rb:100 0.086
Tags: @product
5:46.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.031
Given a computer 0.699
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:7.613
Then Tails is running from USB drive "old" 1.125
And all tps features are active 7.491
When I write some files expected to persist 6.361
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.465
And all persistence configuration files have safe access rights 0.598
And all persistent directories from the old Tails version have safe access rights 4.780
And I take note of which tps features are available 0.596
And I shutdown Tails and wait for the computer to power off 15.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 1:1.240
After features/support/hooks.rb:330 0.207
After features/support/hooks.rb:100 0.009
Tags: @product
4:37.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 22.035
And I log in to a new session 39.182
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.422
And I plug USB drive "to_upgrade" 13.096
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:23.167
Then the running Tails is installed on USB drive "to_upgrade" 56.969
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.269
After features/support/hooks.rb:330 5.677
After features/support/hooks.rb:100 0.000
Tags: @product
4:45.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:15.944
Then all tps features from the old Tails version are active 3.278
And Tails is running from USB drive "to_upgrade" 0.546
And the boot device has safe access rights 14.868
And the expected persistent files created with the old Tails version are present in the filesystem 1.841
And all persistent directories from the old Tails version have safe access rights 8.497
After features/support/hooks.rb:330 5.498
After features/support/hooks.rb:100 0.076
Tags: @product @automatic_upgrade
1:17.424
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.059
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.424
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
Hooks
After features/support/hooks.rb:330 5.982
Error message 
no implicit conversion of nil into String (TypeError)
./features/support/hooks.rb:455:in `exist?'
./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: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:41:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/29/artifact/build-artifacts/02:41:19_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_21014-htpdateerror/29/artifact/build-artifacts/02:41:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/29/artifact/build-artifacts/02:41:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
2:3.288
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 1:12.748
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.618
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.378
And the signing key used by the Upgrader is outdated 0.221
But a current signing key is available on our website 0.000
When the network is plugged 0.241
And Tor is ready 42.103
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.976
After features/support/hooks.rb:330 1.113
After features/support/hooks.rb:100 0.000