Project Number Date
test_Tails_ISO_21014-htpdateerror 17 29 Jun 2025, 22:59

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:32.599 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:37.565
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 39.635
When I start Tails from USB drive "old" with network unplugged 1:48.408
Then the boot device has safe access rights 7.018
And Tails is running from USB drive "old" 0.483
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.362
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.836
After features/support/hooks.rb:100 0.019
Tags: @product
3:1.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.281
And I start Tails from USB drive "old" with network unplugged and I login 2:6.502
Then Tails is running from USB drive "old" 1.030
And I create a persistent partition 43.174
And I take note of which tps features are available 3.301
Then a Tails persistence partition exists on USB drive "old" 0.912
And I shutdown Tails and wait for the computer to power off 6.741
After features/support/hooks.rb:330 0.234
After features/support/hooks.rb:100 0.015
Tags: @product
4:10.255
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.293
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:8.962
Then Tails is running from USB drive "old" 1.097
And all tps features are active 2.697
When I write some files expected to persist 1.786
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.400
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 10.142
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.407
After features/support/hooks.rb:330 0.145
After features/support/hooks.rb:100 0.010
Tags: @product
3:39.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 28.257
And I log in to a new session 25.711
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.244
And I plug USB drive "to_upgrade" 3.363
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.614
Then the running Tails is installed on USB drive "to_upgrade" 42.081
And I unplug USB drive "to_upgrade" 1.923
And I unplug USB drive "__internal" 0.726
After features/support/hooks.rb:330 3.133
After features/support/hooks.rb:100 0.000
Tags: @product
3:15.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:59.974
Then all tps features from the old Tails version are active 2.153
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 4.062
And the expected persistent files created with the old Tails version are present in the filesystem 1.519
And all persistent directories from the old Tails version have safe access rights 7.585
After features/support/hooks.rb:330 2.560
After features/support/hooks.rb:100 0.008
9:3.164
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 30.444
And no SquashFS delta is installed 0.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.844
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.141
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.778
And the file system changes introduced in version 6.3~testoverlayfs are not present 2.117
When the network is plugged 1.118
And Tor is ready 27.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.152
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.759
Given I shutdown Tails and wait for the computer to power off 12.725
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:38.922
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 3.055
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.333
When the network is plugged 0.079
And Tor is ready 24.637
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 12.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.080
Given I shutdown Tails and wait for the computer to power off 6.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:43.993
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 3.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.532
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 2.597
When the network is plugged 0.529
And Tor is ready 22.590
Then the Upgrader considers the system as up-to-date 0.499
# 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 25.464
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.524
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.044
43.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.516
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.419
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.100
And the signing key used by the Upgrader is outdated 0.125
But a current signing key is available on our website 0.000
When the network is plugged 0.202
And Tor is ready 21.502
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.984
After features/support/hooks.rb:330 1.725
After features/support/hooks.rb:100 0.000