Project Number Date
test_Tails_ISO_21014-htpdateerror 16 28 Jun 2025, 23:10

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 26:4.946 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
3:6.972
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.038
Given a computer 0.404
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.134
And I write an old version of the Tails USB image to disk "old" 41.496
When I start Tails from USB drive "old" with network unplugged 2:18.923
Then the boot device has safe access rights 3.902
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 1.088
After features/support/hooks.rb:100 0.064
Tags: @product
3:2.999
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 2:3.882
Then Tails is running from USB drive "old" 1.433
And I create a persistent partition 42.885
And I take note of which tps features are available 4.411
Then a Tails persistence partition exists on USB drive "old" 1.013
And I shutdown Tails and wait for the computer to power off 9.138
After features/support/hooks.rb:330 0.151
After features/support/hooks.rb:100 0.013
Tags: @product
4:9.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.233
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:10.882
Then Tails is running from USB drive "old" 0.706
And all tps features are active 1.992
When I write some files expected to persist 1.762
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 3.201
And I take note of which tps features are available 0.472
And I shutdown Tails and wait for the computer to power off 9.734
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 39.757
After features/support/hooks.rb:330 0.227
After features/support/hooks.rb:100 0.014
Tags: @product
3:10.591
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 without a persistent partition and stopped at Tails Greeter's login screen 11.384
And I log in to a new session 30.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.259
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.054
Then the running Tails is installed on USB drive "to_upgrade" 34.510
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 5.027
After features/support/hooks.rb:100 0.000
Tags: @product
3:9.634
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.230
Given a computer 0.506
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:52.986
Then all tps features from the old Tails version are active 1.986
And Tails is running from USB drive "to_upgrade" 2.669
And the boot device has safe access rights 7.347
And the expected persistent files created with the old Tails version are present in the filesystem 1.670
And all persistent directories from the old Tails version have safe access rights 2.467
After features/support/hooks.rb:330 1.974
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
8:28.550
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.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 18.979
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.563
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.434
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.565
When the network is plugged 0.152
And Tor is ready 30.636
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.231
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 22.297
Given I shutdown Tails and wait for the computer to power off 14.833
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.913
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.579
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.311
# 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.372
When the network is plugged 0.134
And Tor is ready 23.228
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.884
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.683
Given I shutdown Tails and wait for the computer to power off 6.853
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:46.265
Then Tails is running version 6.3~testoverlayfs 0.101
And all tps features are active 6.287
And the file system changes introduced in version 6.3~testoverlayfs are present 1.162
And only the 6.3~testoverlayfs SquashFS delta is installed 0.229
# 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.542
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.845
When the network is plugged 0.101
And Tor is ready 15.769
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/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/usb_upgrade.feature:119:in `And Tor is ready'
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 6.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:28:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/16/artifact/build-artifacts/02:28:34_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/16/artifact/build-artifacts/02:28:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/16/artifact/build-artifacts/02:28:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
56.645
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 14.357
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.641
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.238
And the signing key used by the Upgrader is outdated 0.290
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 27.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.473
After features/support/hooks.rb:330 2.479
After features/support/hooks.rb:100 0.000