Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 24 15 Apr 2025, 19:30

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 41:46.074 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:58.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.060
And I write an old version of the Tails USB image to disk "old" 1:6.918
When I start Tails from USB drive "old" with network unplugged 1:45.444
Then the boot device has safe access rights 3.537
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.122
And udev-watchdog is monitoring the correct device 0.415
And I unplug USB drive "old" 0.267
After features/support/hooks.rb:330 3.564
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.362
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 "old" with network unplugged and I login 1:37.616
Then Tails is running from USB drive "old" 0.459
And I create a persistent partition 32.975
And I take note of which tps features are available 2.621
Then a Tails persistence partition exists on USB drive "old" 0.788
And I shutdown Tails and wait for the computer to power off 8.652
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.146
Then Tails is running from USB drive "old" 0.393
And all tps features are active 2.466
When I write some files expected to persist 2.030
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.266
And all persistence configuration files have safe access rights 0.643
And all persistent directories from the old Tails version have safe access rights 3.216
And I take note of which tps features are available 0.927
And I shutdown Tails and wait for the computer to power off 4.150
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.657
After features/support/hooks.rb:330 0.126
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 13.959
And I log in to a new session 19.571
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.763
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.170
Then the running Tails is installed on USB drive "to_upgrade" 32.229
And I unplug USB drive "to_upgrade" 0.274
And I unplug USB drive "__internal" 0.291
After features/support/hooks.rb:330 1.257
After features/support/hooks.rb:100 0.000
Tags: @product
22:20.330
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.004
Steps
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 22:20.043
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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 11.139 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:05:47)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/24/artifact/build-artifacts/02:05:47_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/24/artifact/build-artifacts/02:05:47_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/24/artifact/build-artifacts/02:05:47_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
7:31.336
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 29.955
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.318
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.524
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.599
When the network is plugged 0.093
And Tor is ready 25.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.107
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.471
Given I shutdown Tails and wait for the computer to power off 14.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.007
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.445
And the file system changes introduced in version 6.2~testoverlayfs are present 0.381
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.382
When the network is plugged 0.091
And Tor is ready 21.464
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.084
Given I shutdown Tails and wait for the computer to power off 6.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.806
Then Tails is running version 6.3~testoverlayfs 0.045
And all tps features are active 2.005
And the file system changes introduced in version 6.3~testoverlayfs are present 0.490
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.299
When the network is plugged 0.081
And Tor is ready 18.575
Then the Upgrader considers the system as up-to-date 0.366
# 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.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.611
After features/support/hooks.rb:330 0.714
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
38.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.901
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.088
And Tor is ready 19.824
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.220
After features/support/hooks.rb:330 1.486
After features/support/hooks.rb:100 0.000