Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 25 16 Aug 2024, 18:40

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 20:7.404 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:8.418
Before features/support/hooks.rb:269 0.004
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 28.946
When I start Tails from USB drive "old" with network unplugged 1:34.135
Then the boot device has safe access rights 3.090
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.120
And udev-watchdog is monitoring the correct device 0.272
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.525
After features/support/hooks.rb:100 0.008
Tags: @product
2:3.859
Before features/support/hooks.rb:269 0.005
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:20.899
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 31.198
And I take note of which tps features are available 1.587
Then a Tails persistence partition exists on USB drive "old" 1.073
And I shutdown Tails and wait for the computer to power off 8.605
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.164
Before features/support/hooks.rb:269 0.004
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.494
Then Tails is running from USB drive "old" 0.572
And all tps features are active 2.074
When I write some files expected to persist 1.726
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 3.164
And I take note of which tps features are available 0.481
And I shutdown Tails and wait for the computer to power off 4.394
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.406
After features/support/hooks.rb:326 0.113
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.034
Before features/support/hooks.rb:269 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 12.376
And I log in to a new session 21.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.891
And I plug USB drive "to_upgrade" 2.468
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.713
Then the running Tails is installed on USB drive "to_upgrade" 18.952
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:326 3.429
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.981
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.842
Then all tps features from the old Tails version are active 1.891
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.344
And the expected persistent files created with the old Tails version are present in the filesystem 1.801
And all persistent directories from the old Tails version have safe access rights 2.530
After features/support/hooks.rb:326 0.624
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
7:37.771
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 32.401
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.304
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.104
And Tor is ready 31.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.580
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.776
Given I shutdown Tails and wait for the computer to power off 10.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.615
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.355
# 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.312
When the network is plugged 0.084
And Tor is ready 20.163
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.271
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.711
Given I shutdown Tails and wait for the computer to power off 4.376
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.490
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.370
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.414
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.326
When the network is plugged 0.071
And Tor is ready 44.724
Then the Upgrader considers the system as up-to-date 0.354
# 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.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.349
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
41.174
Before features/support/hooks.rb:269 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.133
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.909
But a current signing key is available on our website 0.000
When the network is plugged 0.077
And Tor is ready 21.155
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.521
After features/support/hooks.rb:326 1.022
After features/support/hooks.rb:100 0.000