Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 40 25 Apr 2025, 23:05

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 2 10 0 0 87 5 2 7 38:2.336 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
2:1.961
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.091
And I write an old version of the Tails USB image to disk "old" 29.700
When I start Tails from USB drive "old" with network unplugged 1:27.232
Then the boot device has safe access rights 2.795
And Tails is running from USB drive "old" 0.284
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:335 7.095
After features/support/hooks.rb:105 0.009
Tags: @product
2:14.823
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:31.517
Then Tails is running from USB drive "old" 0.332
And I create a persistent partition 32.219
And I take note of which tps features are available 1.452
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.294
After features/support/hooks.rb:335 0.151
After features/support/hooks.rb:105 0.009
Tags: @product
22:4.375
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 22:4.195
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55: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/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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
After features/support/hooks.rb:335 10.770 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:46:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:46:44_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_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:46:44_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:46:44_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:105 0.037
Tags: @product
2:29.331
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.706
And I log in to a new session 18.460
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.810
And I plug USB drive "to_upgrade" 2.391
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.448
Then the running Tails is installed on USB drive "to_upgrade" 23.111
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:335 0.880
After features/support/hooks.rb:105 0.000
Tags: @product
2:8.694
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given a computer 0.179
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.160
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.397
And the expected persistent files created with the old Tails version are present in the filesystem 0.055
Could 
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
After features/support/hooks.rb:335 5.866 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:51:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:51:33_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_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:51:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:51:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/40/artifact/build-artifacts/01:51:33_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
6:28.265
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.078
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.386
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.076
And Tor is ready 17.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.648
Given I shutdown Tails and wait for the computer to power off 8.551
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.165
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.314
# 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.323
When the network is plugged 0.073
And Tor is ready 20.558
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.979
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.809
Given I shutdown Tails and wait for the computer to power off 4.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.823
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.950
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.086
# 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.299
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.081
And Tor is ready 19.845
Then the Upgrader considers the system as up-to-date 0.305
# 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 15.589
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.586
After features/support/hooks.rb:335 0.759
After features/support/hooks.rb:105 0.018
Tags: @product @automatic_upgrade
34.885
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.453
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 16.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.834
After features/support/hooks.rb:335 1.246
After features/support/hooks.rb:105 0.000