Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 31 22 Apr 2025, 19:21

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 22:3.122 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:41.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.276
And I create a 7200 MiB disk named "old" 0.112
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 57.473
When I start Tails from USB drive "old" with network unplugged 1:38.083
Then the boot device has safe access rights 3.356
And Tails is running from USB drive "old" 0.397
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:330 7.509
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.262
And I start Tails from USB drive "old" with network unplugged and I login 1:29.314
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 33.492
And I take note of which tps features are available 1.974
Then a Tails persistence partition exists on USB drive "old" 0.841
And I shutdown Tails and wait for the computer to power off 8.452
After features/support/hooks.rb:330 0.214
After features/support/hooks.rb:100 0.010
Tags: @product
3:10.330
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.284
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:26.714
Then Tails is running from USB drive "old" 0.733
And all tps features are active 2.660
When I write some files expected to persist 2.424
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.616
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 3.144
And I take note of which tps features are available 1.925
And I shutdown Tails and wait for the computer to power off 6.714
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.639
After features/support/hooks.rb:330 0.154
After features/support/hooks.rb:100 0.010
Tags: @product
2:49.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.379
And I log in to a new session 21.339
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.789
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.670
Then the running Tails is installed on USB drive "to_upgrade" 28.478
And I unplug USB drive "to_upgrade" 0.268
And I unplug USB drive "__internal" 0.253
After features/support/hooks.rb:330 0.775
After features/support/hooks.rb:100 0.000
Tags: @product
2:41.412
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.271
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:29.315
Then all tps features from the old Tails version are active 3.786
And Tails is running from USB drive "to_upgrade" 0.480
And the boot device has safe access rights 3.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.526
And all persistent directories from the old Tails version have safe access rights 2.394
After features/support/hooks.rb:330 1.818
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:34.619
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 43.088
And no SquashFS delta is installed 0.607
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.517
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.313
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.496
When the network is plugged 0.081
And Tor is ready 21.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.205
Given I shutdown Tails and wait for the computer to power off 11.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.193
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.325
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.349
# 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.085
And Tor is ready 17.435
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.959
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.553
Given I shutdown Tails and wait for the computer to power off 6.553
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.805
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.583
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.342
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.328
When the network is plugged 0.112
And Tor is ready 20.466
Then the Upgrader considers the system as up-to-date 0.352
# 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.588
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.647
After features/support/hooks.rb:330 0.842
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
49.877
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.498
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.108
And Tor is ready 22.803
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.063
After features/support/hooks.rb:330 1.001
After features/support/hooks.rb:100 0.000