Project Number Date
test_Tails_ISO_21014-htpdateerror 11 23 Jun 2025, 22:02

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:25.468 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:6.361
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 31.599
When I start Tails from USB drive "old" with network unplugged 1:29.588
Then the boot device has safe access rights 2.962
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.511
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.551
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:25.092
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 28.418
And I take note of which tps features are available 2.363
Then a Tails persistence partition exists on USB drive "old" 0.769
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:330 0.258
After features/support/hooks.rb:100 0.028
Tags: @product
2:56.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.553
Then Tails is running from USB drive "old" 0.688
And all tps features are active 2.167
When I write some files expected to persist 1.811
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 2.541
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.526
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.014
After features/support/hooks.rb:330 0.123
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.949
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 without a persistent partition and stopped at Tails Greeter's login screen 10.841
And I log in to a new session 17.713
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.411
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.985
Then the running Tails is installed on USB drive "to_upgrade" 29.082
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:330 2.252
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.864
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.366
Then all tps features from the old Tails version are active 1.500
And Tails is running from USB drive "to_upgrade" 0.458
And the boot device has safe access rights 3.694
And the expected persistent files created with the old Tails version are present in the filesystem 1.299
And all persistent directories from the old Tails version have safe access rights 2.371
After features/support/hooks.rb:330 1.184
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:23.533
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 11.734
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.507
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.558
When the network is plugged 0.079
And Tor is ready 19.516
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.629
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.090
Given I shutdown Tails and wait for the computer to power off 8.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.789
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.252
When the network is plugged 0.063
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.810
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.287
Given I shutdown Tails and wait for the computer to power off 4.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.025
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.285
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.068
And Tor is ready 19.015
Then the Upgrader considers the system as up-to-date 0.391
# 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 14.979
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.720
After features/support/hooks.rb:330 0.701
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
59.611
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 10.471
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.117
And the signing key used by the Upgrader is outdated 0.095
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 47.925
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.612
After features/support/hooks.rb:330 0.639
After features/support/hooks.rb:100 0.000