Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 89 11 Jun 2025, 18:55

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 23:42.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
3:10.913
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.265
And I create a 7200 MiB disk named "old" 0.083
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:17.495
When I start Tails from USB drive "old" with network unplugged 1:47.157
Then the boot device has safe access rights 3.610
And Tails is running from USB drive "old" 0.476
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.336
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:335 7.626
After features/support/hooks.rb:105 0.008
Tags: @product
2:28.563
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Given a computer 0.435
And I start Tails from USB drive "old" with network unplugged and I login 1:42.035
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 33.688
And I take note of which tps features are available 2.523
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 8.622
After features/support/hooks.rb:335 0.297
After features/support/hooks.rb:105 0.009
Tags: @product
3:35.722
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:50.092
Then Tails is running from USB drive "old" 0.489
And all tps features are active 6.448
When I write some files expected to persist 2.014
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.470
And all persistent directories from the old Tails version have safe access rights 3.150
And I take note of which tps features are available 0.738
And I shutdown Tails and wait for the computer to power off 6.491
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.267
After features/support/hooks.rb:335 0.164
After features/support/hooks.rb:105 0.008
Tags: @product
3:6.339
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 23.707
And I log in to a new session 21.512
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.348
And I plug USB drive "to_upgrade" 2.578
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.346
Then the running Tails is installed on USB drive "to_upgrade" 32.243
And I unplug USB drive "to_upgrade" 0.299
And I unplug USB drive "__internal" 0.303
After features/support/hooks.rb:335 3.772
After features/support/hooks.rb:105 0.000
Tags: @product
2:37.815
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given a computer 0.323
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.246
Then all tps features from the old Tails version are active 4.305
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.745
And the expected persistent files created with the old Tails version are present in the filesystem 1.726
And all persistent directories from the old Tails version have safe access rights 3.111
After features/support/hooks.rb:335 1.488
After features/support/hooks.rb:105 0.012
Tags: @product @automatic_upgrade
8:1.434
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 with a persistent partition enabled and logged in 19.685
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.425
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.621
When the network is plugged 0.697
And Tor is ready 23.909
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.528
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.805
Given I shutdown Tails and wait for the computer to power off 11.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:25.390
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.655
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.437
When the network is plugged 0.099
And Tor is ready 19.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.713
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.522
Given I shutdown Tails and wait for the computer to power off 9.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.292
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 3.792
And the file system changes introduced in version 6.3~testoverlayfs are present 0.745
And only the 6.3~testoverlayfs SquashFS delta is installed 0.130
# 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.410
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.372
When the network is plugged 0.108
And Tor is ready 22.677
Then the Upgrader considers the system as up-to-date 0.585
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.828
After features/support/hooks.rb:335 1.411
After features/support/hooks.rb:105 0.055
Tags: @product @automatic_upgrade
42.065
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
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.100
And Tor is ready 19.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.619
After features/support/hooks.rb:335 0.745
After features/support/hooks.rb:105 0.000