Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 7 11 Apr 2025, 00:39

Failures Overview

The following summary displays scenarios that failed.

25:51.248
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.005
And no SquashFS delta is installed 0.190
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.636
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.082
And Tor is ready 21.501
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.169
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.148
Given I shutdown Tails and wait for the computer to power off 8.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.276
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.076
And Tor is ready 19.936
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.071
Given I shutdown Tails and wait for the computer to power off 4.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:58.921
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:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
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:330 10.844

SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:14:58)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/02:14:58_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal

After features/support/hooks.rb:100 0.017
Feature: Using Totem
12.038
Scenario Watching a WebM video over HTTPS
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.037
Then I can watch a WebM video over HTTPs 0.000
undefined method `ipv4?' for #<Resolv::IPv4 192.168.122.6>

    addr.ipv4? && addr.private?
        ^^^^^^ (NoMethodError)
./features/step_definitions/tor.rb:1081:in `block in allow_connecting_to_possibly_rfc1918_host'
./features/step_definitions/tor.rb:1080:in `select'
./features/step_definitions/tor.rb:1080:in `allow_connecting_to_possibly_rfc1918_host'
./features/step_definitions/totem.rb:46:in `/^I can watch a WebM video over HTTPs$/'
features/totem.feature:52:in `Then I can watch a WebM video over HTTPs'
After features/support/hooks.rb:519 0.043
After features/support/hooks.rb:330 5.020

SCENARIO FAILED: 'Watching a WebM video over HTTPS' (at time 05:06:32)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/05:06:32_Watching_a_WebM_video_over_HTTPS.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/05:06:32_Watching_a_WebM_video_over_HTTPS.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/05:06:32_Watching_a_WebM_video_over_HTTPS.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/7/artifact/build-artifacts/05:06:32_Watching_a_WebM_video_over_HTTPS.journal

After features/support/hooks.rb:100 0.000