Project Number Date
test_Tails_ISO_21014-htpdateerror 15 27 Jun 2025, 23:56

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 27:30.841 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
3:16.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.225
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 46.095
When I start Tails from USB drive "old" with network unplugged 2:17.897
Then the boot device has safe access rights 8.014
And Tails is running from USB drive "old" 1.173
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.192
And udev-watchdog is monitoring the correct device 0.967
And I unplug USB drive "old" 0.380
After features/support/hooks.rb:330 4.096
After features/support/hooks.rb:100 0.013
Tags: @product
3:5.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 2:5.578
Then Tails is running from USB drive "old" 0.440
And I create a persistent partition 43.362
And I take note of which tps features are available 4.056
Then a Tails persistence partition exists on USB drive "old" 2.506
And I shutdown Tails and wait for the computer to power off 9.234
After features/support/hooks.rb:330 0.304
After features/support/hooks.rb:100 0.027
Tags: @product
3:59.811
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.019
Given a computer 0.333
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:3.381
Then Tails is running from USB drive "old" 1.262
And all tps features are active 3.743
When I write some files expected to persist 3.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.350
And all persistence configuration files have safe access rights 0.501
And all persistent directories from the old Tails version have safe access rights 2.465
And I take note of which tps features are available 0.493
And I shutdown Tails and wait for the computer to power off 6.859
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.022
After features/support/hooks.rb:330 0.183
After features/support/hooks.rb:100 0.010
Tags: @product
3:32.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 16.617
And I log in to a new session 24.919
And I clone USB drive "old" to a new USB drive "to_upgrade" 10.735
And I plug USB drive "to_upgrade" 3.129
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:3.727
Then the running Tails is installed on USB drive "to_upgrade" 32.584
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.402
After features/support/hooks.rb:330 7.584
After features/support/hooks.rb:100 0.000
Tags: @product
3:19.316
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.286
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:3.201
Then all tps features from the old Tails version are active 6.086
And Tails is running from USB drive "to_upgrade" 0.537
And the boot device has safe access rights 4.343
And the expected persistent files created with the old Tails version are present in the filesystem 1.508
And all persistent directories from the old Tails version have safe access rights 3.352
After features/support/hooks.rb:330 1.282
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
9:31.103
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 17.563
And no SquashFS delta is installed 0.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.693
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.433
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.586
When the network is plugged 0.066
And Tor is ready 30.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.136
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.150
Given I shutdown Tails and wait for the computer to power off 16.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:58.804
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.313
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.422
# 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.329
When the network is plugged 0.078
And Tor is ready 29.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.562
Given I shutdown Tails and wait for the computer to power off 6.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:51.418
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 3.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.613
And only the 6.3~testoverlayfs SquashFS delta is installed 0.104
# 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.323
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.078
And Tor is ready 25.731
Then the Upgrader considers the system as up-to-date 0.472
# 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 29.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.462
After features/support/hooks.rb:330 0.886
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
46.678
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 with a persistent partition enabled and logged in 12.980
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.797
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.173
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.168
And Tor is ready 24.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.081
After features/support/hooks.rb:330 1.512
After features/support/hooks.rb:100 0.000