Project Number Date
test_Tails_ISO_devel 3572 31 Oct 2024, 15:48

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 16:56.188 Failed
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:12.490
Before features/support/hooks.rb:269 0.004
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 33.083
When I start Tails from USB drive "old" with network unplugged 1:32.024
Then the boot device has safe access rights 3.418
And Tails is running from USB drive "old" 1.829
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.108
And udev-watchdog is monitoring the correct device 0.325
And I unplug USB drive "old" 0.227
After features/support/hooks.rb:326 7.049
After features/support/hooks.rb:100 0.010
Tags: @product
2:17.130
Before features/support/hooks.rb:269 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:29.104
Then Tails is running from USB drive "old" 0.421
And I create a persistent partition 34.823
And I take note of which tps features are available 2.153
Then a Tails persistence partition exists on USB drive "old" 1.225
And I shutdown Tails and wait for the computer to power off 9.186
After features/support/hooks.rb:326 0.223
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.820
Before features/support/hooks.rb:269 0.004
Given a computer 0.334
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.289
Then Tails is running from USB drive "old" 1.394
And all tps features are active 2.589
When I write some files expected to persist 2.258
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.495
And I take note of which tps features are available 0.630
And I shutdown Tails and wait for the computer to power off 6.513
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.636
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:57.509
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 30.491
And I log in to a new session 21.159
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.913
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.349
Then the running Tails is installed on USB drive "to_upgrade" 19.168
And I unplug USB drive "to_upgrade" 0.586
And I unplug USB drive "__internal" 0.348
After features/support/hooks.rb:326 3.754
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.212
Before features/support/hooks.rb:269 0.005
Given a computer 1.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:13.151
Then all tps features from the old Tails version are active 2.162
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.897
And the expected persistent files created with the old Tails version are present in the filesystem 1.628
And all persistent directories from the old Tails version have safe access rights 2.789
After features/support/hooks.rb:326 0.771
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:7.466
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.238
And no SquashFS delta is installed 0.230
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.472
When the network is plugged 0.293
And Tor is ready 25.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.992
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.664
Given I shutdown Tails and wait for the computer to power off 9.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.502
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:721:in `greeter_language'
./features/step_definitions/usb.rb:689:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:291:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 5.542 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:03:49)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3572/artifact/build-artifacts/02:03:49_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
45.558
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.325
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.631
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.938
But a current signing key is available on our website 0.000
When the network is plugged 0.498
And Tor is ready 20.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.950
After features/support/hooks.rb:326 1.141
After features/support/hooks.rb:100 0.000