Project Number Date
test_Tails_ISO_21014-htpdateerror 12 24 Jun 2025, 22:22

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 23:10.578 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:21.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 37.561
When I start Tails from USB drive "old" with network unplugged 1:38.339
Then the boot device has safe access rights 3.159
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.363
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:330 3.915
After features/support/hooks.rb:100 0.011
Tags: @product
2:34.645
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:41.196
Then Tails is running from USB drive "old" 1.100
And I create a persistent partition 37.030
And I take note of which tps features are available 4.183
Then a Tails persistence partition exists on USB drive "old" 1.449
And I shutdown Tails and wait for the computer to power off 9.499
After features/support/hooks.rb:330 0.157
After features/support/hooks.rb:100 0.011
Tags: @product
3:28.845
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.878
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:37.295
Then Tails is running from USB drive "old" 1.289
And all tps features are active 2.385
When I write some files expected to persist 1.971
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 4.761
And I take note of which tps features are available 1.123
And I shutdown Tails and wait for the computer to power off 7.046
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 31.366
After features/support/hooks.rb:330 0.211
After features/support/hooks.rb:100 0.011
Tags: @product
3:21.010
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 32.291
And I log in to a new session 23.843
And I clone USB drive "old" to a new USB drive "to_upgrade" 4.631
And I plug USB drive "to_upgrade" 2.569
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.999
Then the running Tails is installed on USB drive "to_upgrade" 31.827
And I unplug USB drive "to_upgrade" 0.628
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:330 2.692
After features/support/hooks.rb:100 0.000
Tags: @product
2:47.064
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:33.142
Then all tps features from the old Tails version are active 3.580
And Tails is running from USB drive "to_upgrade" 0.519
And the boot device has safe access rights 5.148
And the expected persistent files created with the old Tails version are present in the filesystem 1.827
And all persistent directories from the old Tails version have safe access rights 2.622
After features/support/hooks.rb:330 2.475
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
7:55.017
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.436
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.738
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.698
When the network is plugged 0.079
And Tor is ready 22.537
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.162
Given I shutdown Tails and wait for the computer to power off 9.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.219
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.722
And the file system changes introduced in version 6.2~testoverlayfs are present 0.437
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.388
When the network is plugged 0.103
And Tor is ready 49.372
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.778
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.460
Given I shutdown Tails and wait for the computer to power off 4.684
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.542
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 5.634
And the file system changes introduced in version 6.3~testoverlayfs are present 1.044
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.597
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.563
When the network is plugged 0.200
And Tor is ready 23.505
Then the Upgrader considers the system as up-to-date 0.334
# 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 18.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.291
After features/support/hooks.rb:330 0.717
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
42.609
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.415
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.504
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.279
And the signing key used by the Upgrader is outdated 0.189
But a current signing key is available on our website 0.000
When the network is plugged 0.384
And Tor is ready 22.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.482
After features/support/hooks.rb:330 1.835
After features/support/hooks.rb:100 0.000