Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 113 06 Jul 2025, 20: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 26:45.564 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:48.085
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.242
And I create a 7200 MiB disk named "old" 0.079
And I plug USB drive "old" 1.056
And I write an old version of the Tails USB image to disk "old" 42.929
When I start Tails from USB drive "old" with network unplugged 1:58.555
Then the boot device has safe access rights 3.495
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.086
And process "udev-watchdog" is running 0.199
And udev-watchdog is monitoring the correct device 0.719
And I unplug USB drive "old" 0.395
After features/support/hooks.rb:335 5.788
After features/support/hooks.rb:105 0.039
Tags: @product
2:56.383
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.042
Given a computer 0.661
And I start Tails from USB drive "old" with network unplugged and I login 1:55.346
Then Tails is running from USB drive "old" 0.449
And I create a persistent partition 46.996
And I take note of which tps features are available 2.896
Then a Tails persistence partition exists on USB drive "old" 1.204
And I shutdown Tails and wait for the computer to power off 8.827
After features/support/hooks.rb:335 0.153
After features/support/hooks.rb:105 0.010
Tags: @product
3:59.675
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.461
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:5.104
Then Tails is running from USB drive "old" 0.697
And all tps features are active 3.617
When I write some files expected to persist 3.419
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.968
And I take note of which tps features are available 0.707
And I shutdown Tails and wait for the computer to power off 10.937
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.114
After features/support/hooks.rb:335 0.120
After features/support/hooks.rb:105 0.009
Tags: @product
3:31.547
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 18.443
And I log in to a new session 32.604
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.884
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.157
Then the running Tails is installed on USB drive "to_upgrade" 45.201
And I unplug USB drive "to_upgrade" 0.566
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:335 0.741
After features/support/hooks.rb:105 0.000
Tags: @product
3:12.941
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Given a computer 0.224
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:51.853
Then all tps features from the old Tails version are active 6.819
And Tails is running from USB drive "to_upgrade" 0.425
And the boot device has safe access rights 3.546
And the expected persistent files created with the old Tails version are present in the filesystem 2.367
And all persistent directories from the old Tails version have safe access rights 7.703
After features/support/hooks.rb:335 2.695
After features/support/hooks.rb:105 0.070
Tags: @product @automatic_upgrade
9:24.673
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.926
And no SquashFS delta is installed 0.209
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.775
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.156
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.893
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.083
And Tor is ready 31.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.220
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.928
Given I shutdown Tails and wait for the computer to power off 13.864
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.028
Then Tails is running version 6.2~testoverlayfs 0.187
And all tps features are active 5.866
And the file system changes introduced in version 6.2~testoverlayfs are present 0.829
And only the 6.2~testoverlayfs SquashFS delta is installed 0.192
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# 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.522
When the network is plugged 0.301
And Tor is ready 20.343
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.153
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.653
Given I shutdown Tails and wait for the computer to power off 6.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:54.255
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 3.053
And the file system changes introduced in version 6.3~testoverlayfs are present 0.670
And only the 6.3~testoverlayfs SquashFS delta is installed 0.154
# 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.375
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.486
When the network is plugged 0.081
And Tor is ready 28.329
Then the Upgrader considers the system as up-to-date 0.361
# 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 22.045
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.360
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:105 0.019
Tags: @product @automatic_upgrade
52.256
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 13.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.475
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.112
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 26.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.590
After features/support/hooks.rb:335 2.247
After features/support/hooks.rb:105 0.000