Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 47 27 Aug 2024, 14:24

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 38 3 46 0 0 87 4 3 7 18:39.543 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:58.225
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 59.810
When I start Tails from USB drive "old" with network unplugged 1:51.589
Then the boot device has safe access rights 4.225
And Tails is running from USB drive "old" 0.385
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.134
And udev-watchdog is monitoring the correct device 0.410
And I unplug USB drive "old" 0.252
After features/support/hooks.rb:326 3.652
After features/support/hooks.rb:100 0.012
Tags: @product
2:14.631
Before features/support/hooks.rb:269 0.009
Given a computer 0.342
And I start Tails from USB drive "old" with network unplugged and I login 1:26.678
Then Tails is running from USB drive "old" 0.375
And I create a persistent partition 35.698
And I take note of which tps features are available 2.156
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 8.474
After features/support/hooks.rb:326 0.167
After features/support/hooks.rb:100 0.011
Tags: @product
3:2.812
Before features/support/hooks.rb:269 0.007
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.040
Then Tails is running from USB drive "old" 0.396
And all tps features are active 2.358
When I write some files expected to persist 1.845
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.514
And all persistent directories from the old Tails version have safe access rights 2.741
And I take note of which tps features are available 0.619
And I shutdown Tails and wait for the computer to power off 4.530
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.256
After features/support/hooks.rb:326 0.123
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.589
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 15.683
And I log in to a new session 20.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.874
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.303
Then the running Tails is installed on USB drive "to_upgrade" 32.428
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:326 6.778
After features/support/hooks.rb:100 0.000
Tags: @product
3:1.091
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.212
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:0.879
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:683: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:294: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:326 5.328 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:35:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:35:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:35:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:35:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:35:17_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
2:16.626
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:16.626
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:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:82:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And no SquashFS delta is installed 0.000
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.000
And the file system changes introduced in version 6.3~testoverlayfs are not present 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.2~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.2~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.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.378 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:37:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:37:39_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_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:37:39_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:37:39_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:37:39_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
2:10.566
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:269 0.011
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:10.566
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:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/usb_upgrade.feature:127:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.000
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.000
And the signing key used by the Upgrader is outdated 0.000
But a current signing key is available on our website 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.2~testoverlayfs 0.000
After features/support/hooks.rb:326 5.069 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:39:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:39:55_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:39:55_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:39:55_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/47/artifact/build-artifacts/01:39:55_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000