Project Number Date
test_Tails_ISO_21014-htpdateerror 9 21 Jun 2025, 23:45

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 86 1 0 0 0 87 6 1 7 26:47.873 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:22.042
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:1.073
When I start Tails from USB drive "old" with network unplugged 3:14.020
Then the boot device has safe access rights 4.241
And Tails is running from USB drive "old" 0.516
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.413
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 7.179
After features/support/hooks.rb:100 0.032
Tags: @product
3:30.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.768
And I start Tails from USB drive "old" with network unplugged and I login 2:28.010
Then Tails is running from USB drive "old" 0.514
And I create a persistent partition 46.012
And I take note of which tps features are available 4.928
Then a Tails persistence partition exists on USB drive "old" 1.649
And I shutdown Tails and wait for the computer to power off 8.263
After features/support/hooks.rb:330 0.305
After features/support/hooks.rb:100 0.011
Tags: @product
3:59.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:8.432
Then Tails is running from USB drive "old" 2.073
And all tps features are active 3.807
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.398
And all persistent directories from the old Tails version have safe access rights 2.705
And I take note of which tps features are available 0.592
And I shutdown Tails and wait for the computer to power off 9.668
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.680
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.007
Tags: @product
3:10.528
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.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.871
And I log in to a new session 25.851
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.441
And I plug USB drive "to_upgrade" 2.704
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.459
Then the running Tails is installed on USB drive "to_upgrade" 31.601
And I unplug USB drive "to_upgrade" 0.464
And I unplug USB drive "__internal" 6.133
Call 
Call to virDomainDetachDeviceFlags failed: Unable to read from monitor: Connection reset by peer (Guestfs::Error)
./features/support/helpers/vm_helper.rb:367:in `detach_device'
./features/support/helpers/vm_helper.rb:367:in `unplug_drive'
./features/step_definitions/usb.rb:121:in `/^I unplug USB drive "([^"]+)"$/'
features/usb_upgrade.feature:68:in `And I unplug USB drive "__internal"'
Hooks
After features/support/hooks.rb:330 4.503
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 old Tails USB installation from another Tails USB drive' (at time 02:40:47)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/9/artifact/build-artifacts/02:40:47_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21014-htpdateerror/9/artifact/build-artifacts/02:40:47_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
After features/support/hooks.rb:100 0.000
Tags: @product
3:0.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.249
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:44.220
Then all tps features from the old Tails version are active 1.963
And Tails is running from USB drive "to_upgrade" 0.593
And the boot device has safe access rights 7.346
And the expected persistent files created with the old Tails version are present in the filesystem 2.681
And all persistent directories from the old Tails version have safe access rights 3.115
After features/support/hooks.rb:330 1.568
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:3.692
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 with a persistent partition enabled and logged in 19.615
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.412
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.357
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.510
When the network is plugged 0.074
And Tor is ready 25.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 12.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.614
Given I shutdown Tails and wait for the computer to power off 11.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.500
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.740
And the file system changes introduced in version 6.2~testoverlayfs are present 0.482
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.429
# 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.377
When the network is plugged 0.077
And Tor is ready 22.272
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.320
Given I shutdown Tails and wait for the computer to power off 6.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.439
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.034
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.078
And Tor is ready 22.068
Then the Upgrader considers the system as up-to-date 0.351
# 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 17.282
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.880
After features/support/hooks.rb:330 0.956
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
41.694
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.871
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.143
But a current signing key is available on our website 0.000
When the network is plugged 0.094
And Tor is ready 21.050
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.130
After features/support/hooks.rb:330 0.970
After features/support/hooks.rb:100 0.000