Project Number Date
test_Tails_ISO_20635-greeter-threading-fixes 25 10 Nov 2024, 19:48

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:40.595 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:49.427
Before features/support/hooks.rb:269 0.004
Given a computer 0.223
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 1:15.876
When I start Tails from USB drive "old" with network unplugged 1:28.031
Then the boot device has safe access rights 3.166
And Tails is running from USB drive "old" 0.332
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:326 3.543
After features/support/hooks.rb:100 0.015
Tags: @product
2:7.658
Before features/support/hooks.rb:269 0.005
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:23.404
Then Tails is running from USB drive "old" 0.331
And I create a persistent partition 32.980
And I take note of which tps features are available 1.563
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 8.430
After features/support/hooks.rb:326 0.152
After features/support/hooks.rb:100 0.008
Tags: @product
2:56.137
Before features/support/hooks.rb:269 0.005
Given a computer 0.333
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.444
Then Tails is running from USB drive "old" 1.463
And all tps features are active 2.005
When I write some files expected to persist 1.978
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.370
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 2.544
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 6.224
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.852
After features/support/hooks.rb:326 0.122
After features/support/hooks.rb:100 0.009
Tags: @product
2:35.897
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.017
And I log in to a new session 20.629
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.781
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.596
Then the running Tails is installed on USB drive "to_upgrade" 24.053
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.502
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.524
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.135
Then all tps features from the old Tails version are active 1.719
And Tails is running from USB drive "to_upgrade" 0.322
And the boot device has safe access rights 3.354
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:326 0.727
After features/support/hooks.rb:100 0.009
6:19.538
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 12.132
And no SquashFS delta is installed 0.201
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
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.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.069
And Tor is ready 20.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.418
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.026
Given I shutdown Tails and wait for the computer to power off 11.099
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.121
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.344
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.365
# 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.299
When the network is plugged 0.064
And Tor is ready 17.682
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.123
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.463
Given I shutdown Tails and wait for the computer to power off 4.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.233
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.545
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.330
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.080
And Tor is ready 19.425
Then the Upgrader considers the system as up-to-date 0.324
# 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.836
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.012
After features/support/hooks.rb:326 0.728
After features/support/hooks.rb:100 0.016
35.411
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.002
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.830
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 18.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.195
After features/support/hooks.rb:326 1.219
After features/support/hooks.rb:100 0.000