Project Number Date
test_Tails_ISO_15451-support-manual-fsck-on-error 51 28 Aug 2024, 19:34

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:6.027 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:45.533
Before features/support/hooks.rb:269 0.006
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.230
When I start Tails from USB drive "old" with network unplugged 2:7.462
Then the boot device has safe access rights 3.421
And Tails is running from USB drive "old" 0.362
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:326 3.796
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.077
Before features/support/hooks.rb:269 0.005
Given a computer 0.463
And I start Tails from USB drive "old" with network unplugged and I login 1:25.723
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 35.377
And I take note of which tps features are available 1.549
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 10.803
After features/support/hooks.rb:326 0.185
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.001
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.534
Then Tails is running from USB drive "old" 0.527
And all tps features are active 2.169
When I write some files expected to persist 1.844
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.776
And I take note of which tps features are available 0.926
And I shutdown Tails and wait for the computer to power off 4.369
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.947
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.008
Tags: @product
2:40.007
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.560
And I log in to a new session 19.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.866
And I plug USB drive "to_upgrade" 2.474
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.417
Then the running Tails is installed on USB drive "to_upgrade" 26.227
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.283
After features/support/hooks.rb:326 2.814
After features/support/hooks.rb:100 0.000
Tags: @product
3:2.780
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:2.551
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.004 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:36:21)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/51/artifact/build-artifacts/01:36:21_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/51/artifact/build-artifacts/01:36:21_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/51/artifact/build-artifacts/01:36:21_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/51/artifact/build-artifacts/01:36:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
2:17.437
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:17.437
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.192 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:38:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/51/artifact/build-artifacts/01:38:43_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/51/artifact/build-artifacts/01:38:43_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/51/artifact/build-artifacts/01:38:43_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/51/artifact/build-artifacts/01:38:43_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
2:10.188
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 2:10.188
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.288 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 01:40:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_15451-support-manual-fsck-on-error/51/artifact/build-artifacts/01:40:59_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/51/artifact/build-artifacts/01:40:59_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/51/artifact/build-artifacts/01:40:59_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/51/artifact/build-artifacts/01:40:59_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000