Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 66 19 May 2025, 19:07

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:34.417 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:8.408
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 33.342
When I start Tails from USB drive "old" with network unplugged 1:29.750
Then the boot device has safe access rights 3.018
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.198
After features/support/hooks.rb:335 7.081
After features/support/hooks.rb:105 0.009
Tags: @product
2:11.088
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:27.959
Then Tails is running from USB drive "old" 0.409
And I create a persistent partition 31.220
And I take note of which tps features are available 2.323
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.197
After features/support/hooks.rb:335 0.172
After features/support/hooks.rb:105 0.009
Tags: @product
2:52.559
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.089
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.964
When I write some files expected to persist 1.677
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.601
And all persistent directories from the old Tails version have safe access rights 2.495
And I take note of which tps features are available 0.384
And I shutdown Tails and wait for the computer to power off 4.367
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.202
After features/support/hooks.rb:335 0.121
After features/support/hooks.rb:105 0.009
Tags: @product
2:36.135
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 13.593
And I log in to a new session 18.663
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.173
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.993
Then the running Tails is installed on USB drive "to_upgrade" 25.876
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:335 2.333
After features/support/hooks.rb:105 0.000
Tags: @product
2:24.972
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.166
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.008
Then all tps features from the old Tails version are active 1.774
And Tails is running from USB drive "to_upgrade" 0.358
And the boot device has safe access rights 3.833
And the expected persistent files created with the old Tails version are present in the filesystem 1.352
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:335 0.690
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
7:39.904
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 with a persistent partition enabled and logged in 11.710
And no SquashFS delta is installed 0.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.437
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.370
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.574
When the network is plugged 0.066
And Tor is ready 19.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.242
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.883
Given I shutdown Tails and wait for the computer to power off 1:18.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.075
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.092
And the file system changes introduced in version 6.2~testoverlayfs are present 0.335
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.263
When the network is plugged 0.063
And Tor is ready 20.274
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.686
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.062
Given I shutdown Tails and wait for the computer to power off 4.412
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.141
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.707
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.346
When the network is plugged 0.082
And Tor is ready 17.107
Then the Upgrader considers the system as up-to-date 0.331
# 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.861
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.606
After features/support/hooks.rb:335 0.859
After features/support/hooks.rb:105 0.030
Tags: @product @automatic_upgrade
41.346
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 14.446
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.418
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.163
And the signing key used by the Upgrader is outdated 0.143
But a current signing key is available on our website 0.000
When the network is plugged 0.103
And Tor is ready 19.349
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.721
After features/support/hooks.rb:335 0.904
After features/support/hooks.rb:105 0.000