Project Number Date
test_Tails_ISO_21014-htpdateerror 24 06 Jul 2025, 23:13

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:37.130 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:12.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.425
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.095
And I write an old version of the Tails USB image to disk "old" 42.720
When I start Tails from USB drive "old" with network unplugged 2:22.715
Then the boot device has safe access rights 3.642
And Tails is running from USB drive "old" 0.682
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.434
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:330 6.240
After features/support/hooks.rb:100 0.061
Tags: @product
2:59.136
Before features/support/hooks.rb:266 0.012
Before features/support/hooks.rb:273 0.026
Given a computer 0.537
And I start Tails from USB drive "old" with network unplugged and I login 1:56.585
Then Tails is running from USB drive "old" 0.936
And I create a persistent partition 46.830
And I take note of which tps features are available 2.428
Then a Tails persistence partition exists on USB drive "old" 0.749
And I shutdown Tails and wait for the computer to power off 11.067
After features/support/hooks.rb:330 0.406
After features/support/hooks.rb:100 0.022
Tags: @product
3:54.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.262
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:2.274
Then Tails is running from USB drive "old" 1.231
And all tps features are active 2.601
When I write some files expected to persist 1.796
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.265
And all persistence configuration files have safe access rights 0.424
And all persistent directories from the old Tails version have safe access rights 3.430
And I take note of which tps features are available 0.498
And I shutdown Tails and wait for the computer to power off 7.903
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 33.839
After features/support/hooks.rb:330 0.603
After features/support/hooks.rb:100 0.257
Tags: @product
3:12.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.248
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.964
And I log in to a new session 28.548
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.877
And I plug USB drive "to_upgrade" 2.560
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.715
Then the running Tails is installed on USB drive "to_upgrade" 31.054
And I unplug USB drive "to_upgrade" 0.234
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 0.954
After features/support/hooks.rb:100 0.000
Tags: @product
3:11.253
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:55.556
Then all tps features from the old Tails version are active 1.986
And Tails is running from USB drive "to_upgrade" 0.379
And the boot device has safe access rights 3.418
And the expected persistent files created with the old Tails version are present in the filesystem 1.940
And all persistent directories from the old Tails version have safe access rights 7.782
After features/support/hooks.rb:330 1.478
After features/support/hooks.rb:100 0.040
Tags: @product @automatic_upgrade
9:17.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.046
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.181
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.619
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.613
When the network is plugged 0.147
And Tor is ready 26.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.301
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 18.708
Given I shutdown Tails and wait for the computer to power off 14.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:56.798
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.121
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.486
# 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 1.675
When the network is plugged 0.568
And Tor is ready 26.889
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.586
Given I shutdown Tails and wait for the computer to power off 4.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:44.134
Then Tails is running version 6.3~testoverlayfs 0.116
And all tps features are active 4.669
And the file system changes introduced in version 6.3~testoverlayfs are present 1.054
And only the 6.3~testoverlayfs SquashFS delta is installed 0.183
# 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.581
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.754
When the network is plugged 0.085
And Tor is ready 29.065
Then the Upgrader considers the system as up-to-date 0.337
# 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 22.335
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 4.851
After features/support/hooks.rb:330 0.869
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
50.791
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 12.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.075
And Tor is ready 31.229
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.248
After features/support/hooks.rb:330 0.876
After features/support/hooks.rb:100 0.000