Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 45 30 Apr 2025, 02:53

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:32.890 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:9.038
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.922
When I start Tails from USB drive "old" with network unplugged 1:29.522
Then the boot device has safe access rights 3.235
And Tails is running from USB drive "old" 0.398
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:335 3.524
After features/support/hooks.rb:105 0.054
Tags: @product
2:17.036
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:33.147
Then Tails is running from USB drive "old" 0.382
And I create a persistent partition 31.711
And I take note of which tps features are available 2.426
Then a Tails persistence partition exists on USB drive "old" 0.838
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:335 0.225
After features/support/hooks.rb:105 0.011
Tags: @product
3:7.944
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.250
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:28.353
Then Tails is running from USB drive "old" 0.479
And all tps features are active 3.472
When I write some files expected to persist 1.979
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.724
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.567
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.962
After features/support/hooks.rb:335 0.151
After features/support/hooks.rb:105 0.009
Tags: @product
2:37.836
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 without a persistent partition and stopped at Tails Greeter's login screen 12.849
And I log in to a new session 19.345
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.722
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.053
Then the running Tails is installed on USB drive "to_upgrade" 27.000
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:335 2.244
After features/support/hooks.rb:105 0.000
Tags: @product
2:27.364
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:15.895
Then all tps features from the old Tails version are active 1.945
And Tails is running from USB drive "to_upgrade" 0.396
And the boot device has safe access rights 4.193
And the expected persistent files created with the old Tails version are present in the filesystem 1.639
And all persistent directories from the old Tails version have safe access rights 3.090
After features/support/hooks.rb:335 1.280
After features/support/hooks.rb:105 0.020
6:57.080
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.739
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.497
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.468
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.671
When the network is plugged 0.090
And Tor is ready 23.288
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.042
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.986
Given I shutdown Tails and wait for the computer to power off 10.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.279
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.288
And the file system changes introduced in version 6.2~testoverlayfs are present 0.387
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.299
When the network is plugged 0.081
And Tor is ready 22.080
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.085
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.537
Given I shutdown Tails and wait for the computer to power off 4.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.419
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.222
And the file system changes introduced in version 6.3~testoverlayfs are present 0.535
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.317
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.073
And Tor is ready 20.428
Then the Upgrader considers the system as up-to-date 0.339
# 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.995
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.477
After features/support/hooks.rb:335 0.818
After features/support/hooks.rb:105 0.016
56.589
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 27.298
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.451
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.542
And Tor is ready 19.792
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.377
After features/support/hooks.rb:335 2.089
After features/support/hooks.rb:105 0.000