Project Number Date
test_Tails_ISO_21014-htpdateerror 7 19 Jun 2025, 02:42

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:53.209 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:0.256
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.121
When I start Tails from USB drive "old" with network unplugged 1:23.730
Then the boot device has safe access rights 3.148
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.316
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:330 8.525
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:28.120
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 33.271
And I take note of which tps features are available 1.894
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.930
After features/support/hooks.rb:330 0.184
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.529
Then Tails is running from USB drive "old" 0.400
And all tps features are active 1.993
When I write some files expected to persist 2.123
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.372
And all persistence configuration files have safe access rights 0.401
And all persistent directories from the old Tails version have safe access rights 2.844
And I take note of which tps features are available 0.453
And I shutdown Tails and wait for the computer to power off 4.158
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.276
After features/support/hooks.rb:330 0.125
After features/support/hooks.rb:100 0.009
Tags: @product
2:37.450
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.731
And I log in to a new session 19.915
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.796
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.177
Then the running Tails is installed on USB drive "to_upgrade" 27.905
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:330 3.645
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.399
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.330
And the boot device has safe access rights 3.720
And the expected persistent files created with the old Tails version are present in the filesystem 1.619
And all persistent directories from the old Tails version have safe access rights 2.400
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:40.833
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.687
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.404
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.201
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.359
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.065
And Tor is ready 21.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.004
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.386
Given I shutdown Tails and wait for the computer to power off 11.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.715
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.350
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.426
When the network is plugged 0.132
And Tor is ready 19.541
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.722
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.384
Given I shutdown Tails and wait for the computer to power off 4.807
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.809
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.403
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.420
When the network is plugged 0.069
And Tor is ready 20.488
Then the Upgrader considers the system as up-to-date 0.339
# 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 15.403
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.590
After features/support/hooks.rb:330 0.772
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
1:2.901
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.253
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.075
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 50.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.695
After features/support/hooks.rb:330 0.778
After features/support/hooks.rb:100 0.000