Project Number Date
test_Tails_ISO_21014-htpdateerror 10 22 Jun 2025, 22: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 26:0.737 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:54.072
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.196
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 40.120
When I start Tails from USB drive "old" with network unplugged 2:1.961
Then the boot device has safe access rights 5.968
And Tails is running from USB drive "old" 1.275
And there is no persistence partition on USB drive "old" 0.110
And process "udev-watchdog" is running 0.160
And udev-watchdog is monitoring the correct device 0.714
And I unplug USB drive "old" 2.466
After features/support/hooks.rb:330 5.399
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.876
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login 1:48.729
Then Tails is running from USB drive "old" 3.155
And I create a persistent partition 44.403
And I take note of which tps features are available 2.634
Then a Tails persistence partition exists on USB drive "old" 0.725
And I shutdown Tails and wait for the computer to power off 12.016
After features/support/hooks.rb:330 0.693
After features/support/hooks.rb:100 0.035
Tags: @product
3:53.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.026
Given a computer 0.852
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:3.163
Then Tails is running from USB drive "old" 1.210
And all tps features are active 2.357
When I write some files expected to persist 1.877
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.278
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.946
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 7.934
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 32.105
After features/support/hooks.rb:330 0.113
After features/support/hooks.rb:100 0.008
Tags: @product
3:14.572
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.075
And I log in to a new session 24.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.639
And I plug USB drive "to_upgrade" 9.170
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.347
Then the running Tails is installed on USB drive "to_upgrade" 38.462
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 3.847
After features/support/hooks.rb:100 0.000
Tags: @product
3:10.795
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.266
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:54.514
Then all tps features from the old Tails version are active 1.678
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 3.883
And the expected persistent files created with the old Tails version are present in the filesystem 2.032
And all persistent directories from the old Tails version have safe access rights 8.060
After features/support/hooks.rb:330 1.926
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
8:43.994
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 15.437
And no SquashFS delta is installed 0.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.575
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.662
And the file system changes introduced in version 6.3~testoverlayfs are not present 1.010
When the network is plugged 0.188
And Tor is ready 29.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 11.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 16.918
Given I shutdown Tails and wait for the computer to power off 11.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:40.150
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 5.006
And the file system changes introduced in version 6.2~testoverlayfs are present 2.155
And only the 6.2~testoverlayfs SquashFS delta is installed 0.176
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.517
# 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.932
When the network is plugged 0.085
And Tor is ready 23.748
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.618
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 18.998
Given I shutdown Tails and wait for the computer to power off 8.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:37.412
Then Tails is running version 6.3~testoverlayfs 0.233
And all tps features are active 4.586
And the file system changes introduced in version 6.3~testoverlayfs are present 0.723
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.363
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.642
When the network is plugged 0.103
And Tor is ready 22.854
Then the Upgrader considers the system as up-to-date 0.376
# 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 20.704
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.890
After features/support/hooks.rb:330 0.830
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
1:11.768
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.128
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 54.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.774
After features/support/hooks.rb:330 1.526
After features/support/hooks.rb:100 0.000