Project Number Date
test_Tails_ISO_21014-htpdateerror 8 19 Jun 2025, 21:49

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:8.520 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.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.157
When I start Tails from USB drive "old" with network unplugged 1:29.978
Then the boot device has safe access rights 3.450
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:330 3.751
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.953
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:22.027
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 32.802
And I take note of which tps features are available 1.673
Then a Tails persistence partition exists on USB drive "old" 0.746
And I shutdown Tails and wait for the computer to power off 8.238
After features/support/hooks.rb:330 0.179
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.953
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.363
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.000
Then Tails is running from USB drive "old" 0.514
And all tps features are active 1.777
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.178
And all persistence configuration files have safe access rights 0.620
And all persistent directories from the old Tails version have safe access rights 2.669
And I take note of which tps features are available 0.389
And I shutdown Tails and wait for the computer to power off 6.558
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.068
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.009
Tags: @product
2:33.409
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 9.826
And I log in to a new session 18.625
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.376
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.359
Then the running Tails is installed on USB drive "to_upgrade" 26.254
And I unplug USB drive "to_upgrade" 0.217
And I unplug USB drive "__internal" 0.316
After features/support/hooks.rb:330 3.566
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.214
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.385
Then all tps features from the old Tails version are active 1.560
And Tails is running from USB drive "to_upgrade" 0.349
And the boot device has safe access rights 3.492
And the expected persistent files created with the old Tails version are present in the filesystem 1.636
And all persistent directories from the old Tails version have safe access rights 2.649
After features/support/hooks.rb:330 1.149
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:39.474
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 with a persistent partition enabled and logged in 10.740
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.454
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.132
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.482
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.554
When the network is plugged 0.067
And Tor is ready 21.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.155
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.602
Given I shutdown Tails and wait for the computer to power off 8.989
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.676
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.926
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
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.292
# 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.243
When the network is plugged 0.063
And Tor is ready 18.528
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.826
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.736
Given I shutdown Tails and wait for the computer to power off 4.451
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.581
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.016
And the file system changes introduced in version 6.3~testoverlayfs are present 0.587
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.318
When the network is plugged 0.108
And Tor is ready 19.560
Then the Upgrader considers the system as up-to-date 0.323
# 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 16.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.090
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
36.617
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 with a persistent partition enabled and logged in 10.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 19.028
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.935
After features/support/hooks.rb:330 0.820
After features/support/hooks.rb:100 0.000