Project Number Date
test_Tails_ISO_test-suite-early-boot-hooks 11 14 Dec 2024, 20:17

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 41:1.670 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:15.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 34.838
When I start Tails from USB drive "old" with network unplugged 1:35.143
Then the boot device has safe access rights 3.333
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.357
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.748
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:31.977
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 31.366
And I take note of which tps features are available 1.971
Then a Tails persistence partition exists on USB drive "old" 0.777
And I shutdown Tails and wait for the computer to power off 8.512
After features/support/hooks.rb:330 0.192
After features/support/hooks.rb:100 0.010
Tags: @product
3:8.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:31.090
Then Tails is running from USB drive "old" 0.417
And all tps features are active 2.133
When I write some files expected to persist 2.016
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.510
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.387
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.568
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.011
Tags: @product
2:32.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.937
And I log in to a new session 21.325
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.152
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.039
Then the running Tails is installed on USB drive "to_upgrade" 19.150
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.221
After features/support/hooks.rb:330 7.200
After features/support/hooks.rb:100 0.000
Tags: @product
21:50.535
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Steps
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:50.328
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298: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:330 10.830

SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:02:29)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/11/artifact/build-artifacts/02:02:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/11/artifact/build-artifacts/02:02:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/11/artifact/build-artifacts/02:02:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.010
8:20.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.727
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.422
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.089
And Tor is ready 21.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.188
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.601
Given I shutdown Tails and wait for the computer to power off 1:37.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.204
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.475
And the file system changes introduced in version 6.2~testoverlayfs are present 0.359
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.362
# 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.324
When the network is plugged 0.070
And Tor is ready 21.123
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.488
Given I shutdown Tails and wait for the computer to power off 6.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.767
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.460
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.324
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.430
When the network is plugged 0.080
And Tor is ready 23.076
Then the Upgrader considers the system as up-to-date 0.363
# 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 15.491
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.945
After features/support/hooks.rb:330 0.751
After features/support/hooks.rb:100 0.020
38.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 1.149
But a current signing key is available on our website 0.000
When the network is plugged 0.071
And Tor is ready 20.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.459
After features/support/hooks.rb:330 0.777
After features/support/hooks.rb:100 0.000