Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 69 22 May 2025, 18:35

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 20:58.725 Passed
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:15.308
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.339
And I create a 7200 MiB disk named "old" 0.073
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 42.147
When I start Tails from USB drive "old" with network unplugged 1:27.044
Then the boot device has safe access rights 3.434
And Tails is running from USB drive "old" 0.470
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.334
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:335 3.546
After features/support/hooks.rb:105 0.008
Tags: @product
2:10.118
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login 1:25.899
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 31.520
And I take note of which tps features are available 2.600
Then a Tails persistence partition exists on USB drive "old" 0.857
And I shutdown Tails and wait for the computer to power off 8.639
After features/support/hooks.rb:335 0.207
After features/support/hooks.rb:105 0.009
Tags: @product
3:4.648
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.269
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.784
Then Tails is running from USB drive "old" 0.440
And all tps features are active 3.124
When I write some files expected to persist 2.517
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.857
And I take note of which tps features are available 0.636
And I shutdown Tails and wait for the computer to power off 6.599
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.787
After features/support/hooks.rb:335 0.160
After features/support/hooks.rb:105 0.008
Tags: @product
2:57.398
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 19.567
And I log in to a new session 21.012
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.704
And I plug USB drive "to_upgrade" 2.503
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.048
Then the running Tails is installed on USB drive "to_upgrade" 27.119
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:335 3.441
After features/support/hooks.rb:105 0.000
Tags: @product
2:21.666
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.589
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 3.386
And the expected persistent files created with the old Tails version are present in the filesystem 1.382
And all persistent directories from the old Tails version have safe access rights 2.994
After features/support/hooks.rb:335 0.996
After features/support/hooks.rb:105 0.021
Tags: @product @automatic_upgrade
7:33.341
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 46.534
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.444
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.401
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.081
And Tor is ready 21.307
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.769
Given I shutdown Tails and wait for the computer to power off 8.846
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.207
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.542
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.420
# 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.485
When the network is plugged 0.087
And Tor is ready 45.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.597
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.741
Given I shutdown Tails and wait for the computer to power off 4.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.245
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.278
When the network is plugged 0.081
And Tor is ready 17.972
Then the Upgrader considers the system as up-to-date 0.352
# 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.791
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.692
After features/support/hooks.rb:335 0.785
After features/support/hooks.rb:105 0.017
Tags: @product @automatic_upgrade
36.244
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.493
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.110
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 17.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.902
After features/support/hooks.rb:335 1.947
After features/support/hooks.rb:105 0.000