Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 111 04 Jul 2025, 20:04

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 73 1 13 0 0 87 6 1 7 22:41.455 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:2.113
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 43.346
When I start Tails from USB drive "old" with network unplugged 2:12.885
Then the boot device has safe access rights 3.554
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.339
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:335 11.134
After features/support/hooks.rb:105 0.034
Tags: @product
2:57.524
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.026
Given a computer 0.618
And I start Tails from USB drive "old" with network unplugged and I login 1:54.271
Then Tails is running from USB drive "old" 2.169
And I create a persistent partition 45.197
And I take note of which tps features are available 3.590
Then a Tails persistence partition exists on USB drive "old" 0.698
And I shutdown Tails and wait for the computer to power off 10.978
After features/support/hooks.rb:335 0.571
After features/support/hooks.rb:105 0.063
Tags: @product
4:4.354
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.104
Given a computer 1.029
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:4.735
Then Tails is running from USB drive "old" 1.117
And all tps features are active 2.387
When I write some files expected to persist 1.731
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.508
And all persistent directories from the old Tails version have safe access rights 3.424
And I take note of which tps features are available 0.583
And I shutdown Tails and wait for the computer to power off 10.314
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.297
After features/support/hooks.rb:335 0.124
After features/support/hooks.rb:105 0.008
Tags: @product
3:20.153
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.029
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.235
And I log in to a new session 32.206
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.470
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.738
Then the running Tails is installed on USB drive "to_upgrade" 41.372
And I unplug USB drive "to_upgrade" 0.249
And I unplug USB drive "__internal" 0.462
After features/support/hooks.rb:335 2.848
After features/support/hooks.rb:105 0.000
Tags: @product
3:22.996
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:8.449
Then all tps features from the old Tails version are active 5.013
And Tails is running from USB drive "to_upgrade" 0.494
And the boot device has safe access rights 4.712
And the expected persistent files created with the old Tails version are present in the filesystem 1.641
And all persistent directories from the old Tails version have safe access rights 2.461
After features/support/hooks.rb:335 1.742
After features/support/hooks.rb:105 0.007
Tags: @product @automatic_upgrade
5:10.869
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.122
And no SquashFS delta is installed 0.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.559
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.122
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.350
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.088
And Tor is ready 28.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.931
Given I shutdown Tails and wait for the computer to power off 15.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.045
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.705
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.313
# 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.466
When the network is plugged 0.100
And Tor is ready 29.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.781
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.927
cannot 
cannot find TailsUpgraderApplyUpgradeButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/usb.rb:1327:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:107:in `And I can successfully install the incremental upgrade to version 6.3~testoverlayfs'
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
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
After features/support/hooks.rb:335 5.437 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:02:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02: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_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/111/artifact/build-artifacts/02:02:34_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
43.443
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 12.304
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.111
But a current signing key is available on our website 0.000
When the network is plugged 0.125
And Tor is ready 22.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.361
After features/support/hooks.rb:335 0.958
After features/support/hooks.rb:105 0.000