Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 54 07 May 2025, 19:38

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:5.703 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:47.527
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.014
Given a computer 0.300
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.079
And I write an old version of the Tails USB image to disk "old" 43.604
When I start Tails from USB drive "old" with network unplugged 1:57.931
Then the boot device has safe access rights 3.390
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:335 3.743
After features/support/hooks.rb:105 0.010
Tags: @product
2:18.435
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Given a computer 0.512
And I start Tails from USB drive "old" with network unplugged and I login 1:32.181
Then Tails is running from USB drive "old" 0.444
And I create a persistent partition 34.659
And I take note of which tps features are available 2.726
Then a Tails persistence partition exists on USB drive "old" 0.887
And I shutdown Tails and wait for the computer to power off 7.023
After features/support/hooks.rb:335 0.155
After features/support/hooks.rb:105 0.013
Tags: @product
3:39.775
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Given a computer 0.291
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:57.855
Then Tails is running from USB drive "old" 0.441
And all tps features are active 2.409
When I write some files expected to persist 2.411
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.270
And all persistence configuration files have safe access rights 0.533
And all persistent directories from the old Tails version have safe access rights 3.046
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 6.367
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.650
After features/support/hooks.rb:335 0.180
After features/support/hooks.rb:105 0.009
Tags: @product
2:51.668
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 without a persistent partition and stopped at Tails Greeter's login screen 15.945
And I log in to a new session 20.866
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.976
And I plug USB drive "to_upgrade" 3.696
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.215
Then the running Tails is installed on USB drive "to_upgrade" 28.505
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.234
After features/support/hooks.rb:335 4.255
After features/support/hooks.rb:105 0.000
Tags: @product
2:22.941
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.005
Given a computer 0.222
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.916
Then all tps features from the old Tails version are active 1.733
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.722
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.591
After features/support/hooks.rb:335 1.234
After features/support/hooks.rb:105 0.009
Tags: @product @automatic_upgrade
8:4.940
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 28.218
And no SquashFS delta is installed 0.200
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.338
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.092
And Tor is ready 22.740
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.184
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.531
Given I shutdown Tails and wait for the computer to power off 12.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:38.748
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 7.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.196
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.382
# 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.464
When the network is plugged 0.490
And Tor is ready 21.759
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.987
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 14.176
Given I shutdown Tails and wait for the computer to power off 6.646
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:15.825
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.548
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.306
When the network is plugged 0.062
And Tor is ready 19.258
Then the Upgrader considers the system as up-to-date 0.337
# 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.574
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.733
After features/support/hooks.rb:335 0.838
After features/support/hooks.rb:105 0.024
Tags: @product @automatic_upgrade
1:0.414
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 11.608
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.448
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.078
And Tor is ready 47.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.662
After features/support/hooks.rb:335 0.977
After features/support/hooks.rb:105 0.000