Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 65 18 May 2025, 18:29

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 19:7.381 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
1:54.099
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.266
When I start Tails from USB drive "old" with network unplugged 1:19.531
Then the boot device has safe access rights 2.970
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:335 7.551
After features/support/hooks.rb:105 0.009
Tags: @product
2:4.302
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:22.120
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 31.164
And I take note of which tps features are available 1.496
Then a Tails persistence partition exists on USB drive "old" 0.744
And I shutdown Tails and wait for the computer to power off 8.279
After features/support/hooks.rb:335 0.180
After features/support/hooks.rb:105 0.009
Tags: @product
2:52.918
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.926
Then Tails is running from USB drive "old" 0.336
And all tps features are active 2.082
When I write some files expected to persist 2.097
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.243
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.324
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.721
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.119
After features/support/hooks.rb:335 0.144
After features/support/hooks.rb:105 0.010
Tags: @product
2:28.509
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 without a persistent partition and stopped at Tails Greeter's login screen 9.575
And I log in to a new session 18.070
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.477
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.549
Then the running Tails is installed on USB drive "to_upgrade" 21.958
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:335 2.572
After features/support/hooks.rb:105 0.000
Tags: @product
2:15.377
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.104
Then all tps features from the old Tails version are active 1.718
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.246
And the expected persistent files created with the old Tails version are present in the filesystem 1.441
And all persistent directories from the old Tails version have safe access rights 2.368
After features/support/hooks.rb:335 1.266
After features/support/hooks.rb:105 0.008
Tags: @product @automatic_upgrade
6:52.949
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 29.796
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.525
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.323
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.479
When the network is plugged 0.080
And Tor is ready 20.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.236
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.081
Given I shutdown Tails and wait for the computer to power off 8.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.959
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.383
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# 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.269
When the network is plugged 0.076
And Tor is ready 20.377
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.461
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.960
Given I shutdown Tails and wait for the computer to power off 4.465
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.875
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.080
And Tor is ready 18.934
Then the Upgrader considers the system as up-to-date 0.295
# 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.056
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.612
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:105 0.026
Tags: @product @automatic_upgrade
39.223
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 with a persistent partition enabled and logged in 10.874
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.054
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.069
And Tor is ready 21.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.457
After features/support/hooks.rb:335 1.032
After features/support/hooks.rb:105 0.000