Project Number Date
test_Tails_ISO_20138-fix-trezor-support-in-electrum 1 21 Nov 2024, 16:00

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 17:7.001 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:31.158
Before features/support/hooks.rb:269 0.007
Given a computer 0.250
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 44.620
When I start Tails from USB drive "old" with network unplugged 1:40.729
Then the boot device has safe access rights 3.318
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:326 3.621
After features/support/hooks.rb:100 0.013
Tags: @product
2:26.253
Before features/support/hooks.rb:269 0.007
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:31.002
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 42.130
And I take note of which tps features are available 5.208
Then a Tails persistence partition exists on USB drive "old" 0.921
And I shutdown Tails and wait for the computer to power off 6.411
After features/support/hooks.rb:326 0.183
After features/support/hooks.rb:100 0.013
Tags: @product
3:6.263
Before features/support/hooks.rb:269 0.008
Given a computer 0.298
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.463
Then Tails is running from USB drive "old" 0.568
And all tps features are active 2.119
When I write some files expected to persist 2.026
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.289
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.377
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 4.522
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.663
After features/support/hooks.rb:326 0.219
After features/support/hooks.rb:100 0.011
Tags: @product
3:3.791
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.195
And I log in to a new session 24.502
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.060
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.000
Then the running Tails is installed on USB drive "to_upgrade" 26.026
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.284
After features/support/hooks.rb:326 4.099
After features/support/hooks.rb:100 0.000
Tags: @product
2:35.524
Before features/support/hooks.rb:269 0.011
Given a computer 0.280
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:23.687
Then all tps features from the old Tails version are active 3.466
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.594
And all persistent directories from the old Tails version have safe access rights 2.731
After features/support/hooks.rb:326 1.029
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
2:41.692
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.010
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27.148
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.944
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.468
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.490
When the network is plugged 0.544
And Tor is ready 22.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.496
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.735
Given I shutdown Tails and wait for the computer to power off 11.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.802
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/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/usb.rb:669:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700: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.366 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:50:05)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20138-fix-trezor-support-in-electrum/1/artifact/build-artifacts/01:50:05_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_20138-fix-trezor-support-in-electrum/1/artifact/build-artifacts/01:50:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20138-fix-trezor-support-in-electrum/1/artifact/build-artifacts/01:50:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20138-fix-trezor-support-in-electrum/1/artifact/build-artifacts/01:50:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
42.318
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 13.679
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.796
But a current signing key is available on our website 0.000
When the network is plugged 0.252
And Tor is ready 19.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.839
After features/support/hooks.rb:326 0.816
After features/support/hooks.rb:100 0.000