Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 20 18 Apr 2025, 23:21

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:55.801 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
1:59.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 29.533
When I start Tails from USB drive "old" with network unplugged 1:24.339
Then the boot device has safe access rights 3.090
And Tails is running from USB drive "old" 0.356
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:330 7.103
After features/support/hooks.rb:100 0.008
Tags: @product
2:18.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:35.837
Then Tails is running from USB drive "old" 0.407
And I create a persistent partition 31.075
And I take note of which tps features are available 2.213
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 8.255
After features/support/hooks.rb:330 0.181
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.006
Then Tails is running from USB drive "old" 0.413
And all tps features are active 2.256
When I write some files expected to persist 1.860
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.322
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.598
And I take note of which tps features are available 0.512
And I shutdown Tails and wait for the computer to power off 6.542
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.044
After features/support/hooks.rb:330 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.279
And I log in to a new session 21.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.591
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.281
Then the running Tails is installed on USB drive "to_upgrade" 26.486
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:330 0.912
After features/support/hooks.rb:100 0.000
Tags: @product
22:0.876
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.007
Steps
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 22:0.685
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.885

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

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/20/artifact/build-artifacts/02:00:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/20/artifact/build-artifacts/02:00:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/20/artifact/build-artifacts/02:00:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal

After features/support/hooks.rb:100 0.007
9:25.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.496
And no SquashFS delta is installed 0.300
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
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.522
When the network is plugged 0.121
And Tor is ready 22.941
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 15.351
Given I shutdown Tails and wait for the computer to power off 1:28.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:39.669
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 3.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.327
And only the 6.2~testoverlayfs SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.403
# 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.369
When the network is plugged 0.084
And Tor is ready 47.737
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.637
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.844
Given I shutdown Tails and wait for the computer to power off 4.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.394
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.426
And the file system changes introduced in version 6.3~testoverlayfs are present 0.617
And only the 6.3~testoverlayfs SquashFS delta is installed 0.099
# 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.449
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.078
And Tor is ready 20.985
Then the Upgrader considers the system as up-to-date 0.362
# 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 16.171
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.531
After features/support/hooks.rb:330 0.733
After features/support/hooks.rb:100 0.060
37.563
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 11.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.343
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 19.141
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.722
After features/support/hooks.rb:330 0.715
After features/support/hooks.rb:100 0.000