Project Number Date
test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution 25 24 Apr 2025, 00:43

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Time syncing 78 1 1 0 0 80 9 1 10 8:42.654 Failed
Feature Time syncing
As a Tails user I want Tor to work properly And for that I need a reasonably accurate system clock
24.126
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.003
Given I have started Tails from DVD without network and logged in 8.106
When the network is plugged 0.221
And I successfully configure Tor 15.753
Then the system clock is less than 5 minutes incorrect 0.045
After features/support/hooks.rb:519 0.350
After features/support/hooks.rb:330 0.644
After features/support/hooks.rb:100 0.000
28.084
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.002
Given I have started Tails from DVD without network and logged in 8.100
When the network is plugged 0.066
And the Tor Connection Assistant autostarts 3.890
And I configure some normal bridges in the Tor Connection Assistant 11.982
And I wait until Tor is ready 3.984
Then the system clock is less than 5 minutes incorrect 0.059
After features/support/hooks.rb:519 0.254
After features/support/hooks.rb:330 0.749
After features/support/hooks.rb:100 0.000
30.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.002
Given I have started Tails from DVD without network and logged in 8.145
When I bump the system time with "+1 day" 0.259
And I capture all network traffic 0.003
And the network is plugged 0.149
And the Tor Connection Assistant autostarts 3.928
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.040
And I wait until Tor is ready 1.978
Then the system clock is less than 5 minutes incorrect 0.060
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.464

Warning: these queries were allowed but not needed: ["fedoraproject.org."]

After features/support/hooks.rb:519 0.269
After features/support/hooks.rb:330 0.994
After features/support/hooks.rb:100 0.034
1:22.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.003
Given I have started Tails from DVD without network and logged in 8.041
When I bump the system time with "-15 days" 0.257
And I warm reboot the computer 0.018
And the computer reboots Tails 1:13.298
Then Tails' hardware clock is close to the host system's time 0.609
After features/support/hooks.rb:519 0.119
After features/support/hooks.rb:330 0.664
After features/support/hooks.rb:100 0.030
2:2.809
Scenario Anti-test: Changes to the hardware clock are kept when rebooting
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.146
When I bump the hardware clock's time with "-15 days" 3.021
And I warm reboot the computer 0.013
And the computer reboots Tails 1:51.627
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:459:in `block in <top (required)>' (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/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:45:in `And the computer reboots Tails'
Then the hardware clock is still off by "-15 days" 0.000
After features/support/hooks.rb:519 0.039
After features/support/hooks.rb:330 4.819

SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:15:45)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/25/artifact/build-artifacts/00:15:45_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/25/artifact/build-artifacts/00:15:45_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/25/artifact/build-artifacts/00:15:45_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-test-suite-reject-allow-internal-dns-resolution/25/artifact/build-artifacts/00:15:45_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal

After features/support/hooks.rb:100 0.006
58.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.002
Given a computer 0.150
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.020
And I start the computer 1.001
And the computer boots Tails 56.934
Then the system clock is just past Tails' source date 0.170
After features/support/hooks.rb:519 0.130
After features/support/hooks.rb:330 0.974
After features/support/hooks.rb:100 0.005
31.894
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Before features/support/hooks.rb:511 0.002
Given I have started Tails from DVD without network and logged in 8.075
And I make sure time sync before Tor connects times out 1.205
When the network is plugged 0.066
And I successfully configure Tor 22.454
Then the system clock is less than 5 minutes incorrect 0.093
After features/support/hooks.rb:519 0.312
After features/support/hooks.rb:330 0.673
After features/support/hooks.rb:100 0.000
1:2.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.003
Given I have started Tails from DVD without network and logged in 8.086
When I bump the system time with "+8 hours +15 minutes" 0.258
And all notifications have disappeared 4.115
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.092
And the network is plugged 0.069
And the Tor Connection Assistant autostarts 3.449
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.263
And I click "Connect to Tor" 1.178
And the Tor Connection Assistant fails to connect to Tor 15.796
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.922
Then the system clock is less than 20 minutes incorrect 0.283
When I click "Connect to Tor" 1.159
Then I wait until Tor is ready 7.138
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.460
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.058
After features/support/hooks.rb:519 0.251
After features/support/hooks.rb:330 0.888
After features/support/hooks.rb:100 0.065
59.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:511 0.002
Given I have started Tails from DVD without network and logged in 8.907
When I bump the system time with "+8 hours +15 minutes" 0.274
And all notifications have disappeared 4.475
And I capture all network traffic 0.002
And the network is plugged 0.061
And the Tor Connection Assistant autostarts 3.554
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.316
And I click "Connect to Tor" 1.190
Then the Tor Connection Assistant reports that it failed to connect 11.740
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.955
Then the system clock is less than 20 minutes incorrect 0.278
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.374
When I click "Connect to Tor" 1.149
Then I wait until Tor is ready 7.239
And all Internet traffic has only flowed through the configured bridges 0.502
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.060
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.386
After features/support/hooks.rb:519 0.270
After features/support/hooks.rb:330 0.881
After features/support/hooks.rb:100 0.045
23.396
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:511 0.002
Given I have started Tails from DVD without network and logged in 8.086
And I make sure time sync before Tor connects uses a fake connectivity check service 1.217
And the network is plugged 0.061
And Tor is ready 12.462
Then the fake connectivity check service has received a new HTTP request 0.000
When I make NetworkManager perform a connectivity check 1.564
Then the fake connectivity check service has received a new HTTP request 0.000
And the HTTP requests received by the fake connectivity check service are identical 0.002
After features/support/hooks.rb:519 0.416
After features/support/hooks.rb:330 0.667
After features/support/hooks.rb:100 0.000