Project Number Date
test_Tails_ISO_21014-htpdateerror 25 08 Jul 2025, 03:17

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 67 3 17 0 0 87 4 3 7 33:28.471 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:21.583
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:2.992
When I start Tails from USB drive "old" with network unplugged 3:4.069
Then the boot device has safe access rights 12.072
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.379
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 17.476
After features/support/hooks.rb:100 0.021
Tags: @product
4:14.108
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login 2:36.438
Then Tails is running from USB drive "old" 3.168
And I create a persistent partition 1:5.285
And I take note of which tps features are available 3.832
Then a Tails persistence partition exists on USB drive "old" 9.544
And I shutdown Tails and wait for the computer to power off 15.554
After features/support/hooks.rb:330 1.546
After features/support/hooks.rb:100 0.108
Tags: @product
2:10.258
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.077
Steps
Given a computer 1.705
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.552
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284:in `block in <top (required)>' (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:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
Hooks
After features/support/hooks.rb:330 9.117
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: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:44:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:44:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:44:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:44:48_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv

After features/support/hooks.rb:100 0.128
Tags: @product
4:5.806
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.156
And I log in to a new session 36.909
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.152
And I plug USB drive "to_upgrade" 12.105
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:16.852
Then the running Tails is installed on USB drive "to_upgrade" 42.137
And I unplug USB drive "to_upgrade" 0.273
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 4.025
After features/support/hooks.rb:100 0.000
Tags: @product
4:36.600
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.009
Steps
Given a computer 0.254
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:19.860
Then all tps features from the old Tails version are active 5.436
And Tails is running from USB drive "to_upgrade" 6.780
And the boot device has safe access rights 4.204
And the expected persistent files created with the old Tails version are present in the filesystem 0.063
Could not find expected file in persistent directory /home/amnesia/Persistent.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/misc_helpers.rb:21:in `assert_vmcommand_success'
./features/step_definitions/usb.rb:1097:in `block (2 levels) in <top (required)>'
./features/step_definitions/usb.rb:1096:in `each'
./features/step_definitions/usb.rb:1096:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
Hooks
After features/support/hooks.rb:330 8.794
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: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:53:43)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:53:43_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:53:43_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/02:53:43_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

After features/support/hooks.rb:100 0.345
12:42.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.274
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 46.988
And no SquashFS delta is installed 0.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.978
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.068
And Tor is ready 39.955
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 17.297
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22.975
Given I shutdown Tails and wait for the computer to power off 19.976
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:25.714
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 10.636
And the file system changes introduced in version 6.2~testoverlayfs are present 1.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.261
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.544
# 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.421
When the network is plugged 0.105
And Tor is ready 40.097
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.013
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 31.516
Given I shutdown Tails and wait for the computer to power off 9.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:54.772
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.373
And the file system changes introduced in version 6.3~testoverlayfs are present 0.496
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.358
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 1.037
When the network is plugged 0.880
And Tor is ready 30.467
Then the Upgrader considers the system as up-to-date 0.406
# 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 26.126
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 8.546
After features/support/hooks.rb:330 3.276
After features/support/hooks.rb:100 0.056
1:17.356
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:17.356
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:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
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 signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 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
Hooks
After features/support/hooks.rb:330 6.860
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 a Tails whose signing key is outdated' (at time 03:07:56)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/03:07:56_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/03:07:56_Upgrading_a_Tails_whose_signing_key_is_outdated.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/25/artifact/build-artifacts/03:07:56_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv

After features/support/hooks.rb:100 0.000