Project Number Date
test_Tails_ISO_21014-htpdateerror 4 15 Jun 2025, 21: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 19:12.116 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:2.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 32.270
When I start Tails from USB drive "old" with network unplugged 1:25.173
Then the boot device has safe access rights 3.151
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 0.997
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.273
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 1:23.457
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 29.982
And I take note of which tps features are available 1.948
Then a Tails persistence partition exists on USB drive "old" 0.750
And I shutdown Tails and wait for the computer to power off 8.579
After features/support/hooks.rb:330 0.205
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.092
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.506
Then Tails is running from USB drive "old" 0.589
And all tps features are active 2.195
When I write some files expected to persist 3.264
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.392
And all persistent directories from the old Tails version have safe access rights 2.514
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 6.549
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.140
After features/support/hooks.rb:330 0.097
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.386
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 10.070
And I log in to a new session 18.429
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.427
And I plug USB drive "to_upgrade" 2.419
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.155
Then the running Tails is installed on USB drive "to_upgrade" 25.468
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:330 3.581
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.475
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.245
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.331
Then all tps features from the old Tails version are active 1.631
And Tails is running from USB drive "to_upgrade" 0.401
And the boot device has safe access rights 3.042
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.453
After features/support/hooks.rb:330 0.706
After features/support/hooks.rb:100 0.009
6:44.058
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 11.833
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.542
When the network is plugged 0.066
And Tor is ready 18.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.008
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 20.120
Given I shutdown Tails and wait for the computer to power off 8.690
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.158
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.091
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.312
When the network is plugged 0.085
And Tor is ready 19.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.114
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.252
Given I shutdown Tails and wait for the computer to power off 4.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.161
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.333
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.319
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.404
When the network is plugged 0.081
And Tor is ready 19.463
Then the Upgrader considers the system as up-to-date 0.317
# 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.065
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.552
After features/support/hooks.rb:330 0.639
After features/support/hooks.rb:100 0.018
35.871
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 9.636
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.088
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 19.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.652
After features/support/hooks.rb:330 1.150
After features/support/hooks.rb:100 0.000