Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 73 26 May 2025, 18:39

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:39.557 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:3.347
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.899
When I start Tails from USB drive "old" with network unplugged 1:26.194
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:335 6.902
After features/support/hooks.rb:105 0.009
Tags: @product
2:6.391
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:24.090
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 30.923
And I take note of which tps features are available 1.712
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 8.339
After features/support/hooks.rb:335 0.242
After features/support/hooks.rb:105 0.009
Tags: @product
2:59.209
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.375
Then Tails is running from USB drive "old" 1.162
And all tps features are active 2.116
When I write some files expected to persist 3.035
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.460
And I take note of which tps features are available 0.562
And I shutdown Tails and wait for the computer to power off 6.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.173
After features/support/hooks.rb:335 0.161
After features/support/hooks.rb:105 0.013
Tags: @product
2:50.122
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 19.082
And I log in to a new session 19.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.830
And I plug USB drive "to_upgrade" 2.592
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.711
Then the running Tails is installed on USB drive "to_upgrade" 29.054
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.228
After features/support/hooks.rb:335 3.761
After features/support/hooks.rb:105 0.000
Tags: @product
2:20.349
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.269
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.296
Then all tps features from the old Tails version are active 1.756
And Tails is running from USB drive "to_upgrade" 0.369
And the boot device has safe access rights 3.655
And the expected persistent files created with the old Tails version are present in the filesystem 1.485
And all persistent directories from the old Tails version have safe access rights 2.514
After features/support/hooks.rb:335 1.379
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
7:40.989
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 37.841
And no SquashFS delta is installed 0.255
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.591
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.450
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.581
When the network is plugged 0.097
And Tor is ready 23.879
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.791
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.615
Given I shutdown Tails and wait for the computer to power off 8.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.342
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.770
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.110
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.406
# 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.371
When the network is plugged 0.107
And Tor is ready 48.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.103
Given I shutdown Tails and wait for the computer to power off 4.720
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.932
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.515
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.379
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.087
And Tor is ready 21.042
Then the Upgrader considers the system as up-to-date 0.310
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.657
After features/support/hooks.rb:335 0.743
After features/support/hooks.rb:105 0.018
Tags: @product @automatic_upgrade
39.148
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 12.179
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.502
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.105
And Tor is ready 19.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.777
After features/support/hooks.rb:335 1.283
After features/support/hooks.rb:105 0.000