Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 105 28 Jun 2025, 20:25

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 25:45.354 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:55.155
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.321
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 39.976
When I start Tails from USB drive "old" with network unplugged 2:2.153
Then the boot device has safe access rights 10.368
And Tails is running from USB drive "old" 0.406
And there is no persistence partition on USB drive "old" 0.094
And process "udev-watchdog" is running 0.157
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:335 3.588
After features/support/hooks.rb:105 0.012
Tags: @product
2:49.810
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.289
And I start Tails from USB drive "old" with network unplugged and I login 1:52.972
Then Tails is running from USB drive "old" 0.949
And I create a persistent partition 41.770
And I take note of which tps features are available 2.147
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 10.876
After features/support/hooks.rb:335 0.610
After features/support/hooks.rb:105 0.035
Tags: @product
3:46.160
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.018
Given a computer 0.622
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:48.301
Then Tails is running from USB drive "old" 0.388
And all tps features are active 2.724
When I write some files expected to persist 2.063
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 2.056
And all persistent directories from the old Tails version have safe access rights 6.258
And I take note of which tps features are available 0.509
And I shutdown Tails and wait for the computer to power off 6.560
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.469
After features/support/hooks.rb:335 0.122
After features/support/hooks.rb:105 0.007
Tags: @product
3:6.089
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 without a persistent partition and stopped at Tails Greeter's login screen 14.438
And I log in to a new session 27.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.250
And I plug USB drive "to_upgrade" 2.552
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.979
Then the running Tails is installed on USB drive "to_upgrade" 31.859
And I unplug USB drive "to_upgrade" 0.651
And I unplug USB drive "__internal" 0.235
After features/support/hooks.rb:335 0.942
After features/support/hooks.rb:105 0.000
Tags: @product
3:0.945
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:50.534
Then all tps features from the old Tails version are active 2.130
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.167
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.894
After features/support/hooks.rb:335 3.624
After features/support/hooks.rb:105 0.015
Tags: @product @automatic_upgrade
9:20.502
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.853
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.513
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.148
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.692
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.424
When the network is plugged 0.088
And Tor is ready 29.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.953
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.507
Given I shutdown Tails and wait for the computer to power off 12.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.613
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 3.498
And the file system changes introduced in version 6.2~testoverlayfs are present 0.355
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.304
When the network is plugged 0.076
And Tor is ready 30.811
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.673
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.875
Given I shutdown Tails and wait for the computer to power off 8.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.384
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 6.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.815
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.478
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.426
When the network is plugged 0.084
And Tor is ready 51.781
Then the Upgrader considers the system as up-to-date 0.349
# 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 20.758
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.933
After features/support/hooks.rb:335 1.503
After features/support/hooks.rb:105 0.040
Tags: @product @automatic_upgrade
46.689
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.644
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.154
And the signing key used by the Upgrader is outdated 0.120
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 27.416
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.433
After features/support/hooks.rb:335 0.703
After features/support/hooks.rb:105 0.000