Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 108 01 Jul 2025, 20:17

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 26:39.692 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:46.715
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.323
And I create a 7200 MiB disk named "old" 0.086
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 41.654
When I start Tails from USB drive "old" with network unplugged 1:59.189
Then the boot device has safe access rights 3.198
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.101
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.253
After features/support/hooks.rb:335 12.353
After features/support/hooks.rb:105 0.010
Tags: @product
2:46.270
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login 1:48.642
Then Tails is running from USB drive "old" 0.687
And I create a persistent partition 41.451
And I take note of which tps features are available 5.547
Then a Tails persistence partition exists on USB drive "old" 2.628
And I shutdown Tails and wait for the computer to power off 7.065
After features/support/hooks.rb:335 0.341
After features/support/hooks.rb:105 0.011
Tags: @product
4:20.513
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:18.352
Then Tails is running from USB drive "old" 0.435
And all tps features are active 2.522
When I write some files expected to persist 2.044
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.562
And all persistence configuration files have safe access rights 3.371
And all persistent directories from the old Tails version have safe access rights 6.187
And I take note of which tps features are available 0.538
And I shutdown Tails and wait for the computer to power off 6.207
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 40.045
After features/support/hooks.rb:335 0.178
After features/support/hooks.rb:105 0.014
Tags: @product
3:19.624
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.363
And I log in to a new session 23.433
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.794
And I plug USB drive "to_upgrade" 3.792
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:59.051
Then the running Tails is installed on USB drive "to_upgrade" 34.718
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:335 1.460
After features/support/hooks.rb:105 0.000
Tags: @product
3:12.240
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.259
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:55.820
Then all tps features from the old Tails version are active 2.498
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 6.148
And the expected persistent files created with the old Tails version are present in the filesystem 3.110
And all persistent directories from the old Tails version have safe access rights 3.998
After features/support/hooks.rb:335 1.799
After features/support/hooks.rb:105 0.010
Tags: @product @automatic_upgrade
9:1.073
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 16.154
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.423
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.120
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.412
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.737
When the network is plugged 0.064
And Tor is ready 28.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.760
Given I shutdown Tails and wait for the computer to power off 12.696
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 3:3.321
Then Tails is running version 6.2~testoverlayfs 1.124
And all tps features are active 6.559
And the file system changes introduced in version 6.2~testoverlayfs are present 0.974
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.314
When the network is plugged 0.077
And Tor is ready 23.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 11.282
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.283
Given I shutdown Tails and wait for the computer to power off 10.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.892
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 7.229
And the file system changes introduced in version 6.3~testoverlayfs are present 0.784
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.380
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.442
When the network is plugged 0.175
And Tor is ready 22.811
Then the Upgrader considers the system as up-to-date 0.327
# 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.090
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.569
After features/support/hooks.rb:335 0.749
After features/support/hooks.rb:105 0.030
Tags: @product @automatic_upgrade
1:13.254
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 33.983
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.364
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.276
But a current signing key is available on our website 0.000
When the network is plugged 0.146
And Tor is ready 24.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 14.414
After features/support/hooks.rb:335 1.881
After features/support/hooks.rb:105 0.000