Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 60 13 May 2025, 19:33

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 22:26.854 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:9.575
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 32.035
When I start Tails from USB drive "old" with network unplugged 1:31.412
Then the boot device has safe access rights 3.706
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.266
After features/support/hooks.rb:335 3.781
After features/support/hooks.rb:105 0.010
Tags: @product
2:10.051
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 1:26.859
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 32.937
And I take note of which tps features are available 2.276
Then a Tails persistence partition exists on USB drive "old" 0.896
And I shutdown Tails and wait for the computer to power off 6.464
After features/support/hooks.rb:335 0.231
After features/support/hooks.rb:105 0.011
Tags: @product
3:4.571
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.297
Then Tails is running from USB drive "old" 0.432
And all tps features are active 2.227
When I write some files expected to persist 1.912
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.312
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 2.568
And I take note of which tps features are available 1.374
And I shutdown Tails and wait for the computer to power off 6.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.587
After features/support/hooks.rb:335 0.195
After features/support/hooks.rb:105 0.023
Tags: @product
2:58.244
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 26.622
And I log in to a new session 22.063
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.693
And I plug USB drive "to_upgrade" 2.467
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.603
Then the running Tails is installed on USB drive "to_upgrade" 30.377
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:335 2.110
After features/support/hooks.rb:105 0.000
Tags: @product
2:32.639
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:20.062
Then all tps features from the old Tails version are active 2.205
And Tails is running from USB drive "to_upgrade" 0.328
And the boot device has safe access rights 3.878
And the expected persistent files created with the old Tails version are present in the filesystem 3.230
And all persistent directories from the old Tails version have safe access rights 2.717
After features/support/hooks.rb:335 1.874
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
8:46.066
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 25.662
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.510
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.331
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.425
And Tor is ready 50.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.841
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.176
Given I shutdown Tails and wait for the computer to power off 11.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:21.081
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 8.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.367
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.372
# 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.348
When the network is plugged 0.108
And Tor is ready 16.598
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 9.319
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.451
Given I shutdown Tails and wait for the computer to power off 6.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:33.553
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.812
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.092
And Tor is ready 50.002
Then the Upgrader considers the system as up-to-date 0.307
# 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 16.286
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.180
After features/support/hooks.rb:335 1.071
After features/support/hooks.rb:105 0.016
Tags: @product @automatic_upgrade
45.706
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 16.637
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.406
And Tor is ready 18.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.793
After features/support/hooks.rb:335 2.687
After features/support/hooks.rb:105 0.000