Project

General

Profile

Bug #11462

Bug #10288: Fix newly identified issues to make our test suite more robust and faster

"I2P is running" test is fragile: may fail when the time has not sync'ed yet

Added by intrigeri over 3 years ago. Updated over 3 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
-
Start date:
05/23/2016
Due date:
% Done:

0%

Feature Branch:
test/11462-I2P-is-running-is-fragile
Type of work:
Code
Blueprint:
Starter:
Affected tool:
I2P

Description

I don't know if that's a mere network glitch, or if we should wait for the time to have sync'ed before we start I2P.

  Scenario: I2P displays a notice when it fails to start               # features/i2p.feature:87
calling as root: echo 'hello?'
call returned: [0, "hello?\n", ""]
[log] CLICK on (1024,384)
calling as root: /sbin/ifconfig eth0 | grep -q 'inet addr'
call returned: [1, "", ""]
calling as root: date -s '@1463923929'
call returned: [0, "Sun May 22 13:32:09 UTC 2016\n", ""]
    Given I have started Tails from DVD with I2P enabled and logged in # features/step_definitions/snapshots.rb:199
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
    And I2P is not running                                             # features/step_definitions/i2p.rb:1
calling as root: pidof -x -o '%PPID' nc
call returned: [1, "", ""]
spawning as root: nc -l -p 7657 -t 127.0.0.1
calling as root: pidof -x -o '%PPID' nc
call returned: [0, "2819\n", ""]
    And I block the I2P router console port                            # features/step_definitions/i2p.rb:55
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
    Then I2P is not running                                            # features/step_definitions/i2p.rb:1
    When the network is plugged                                        # features/step_definitions/common_steps.rb:161
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [1, "", ""]
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [1, "", ""]
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [1, "", ""]
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [3, "", ""]
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [3, "", ""]
calling as root: /usr/local/sbin/tor-has-bootstrapped
call returned: [0, "", ""]
    And Tor has built a circuit                                        # features/step_definitions/common_steps.rb:390
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
calling as root: systemctl --quiet is-active i2p
call returned: [3, "", ""]
    Then I2P is running                                                # features/step_definitions/i2p.rb:1
      try_for() timeout expired (Timeout::Error)
      ./features/support/helpers/misc_helpers.rb:83:in `rescue in try_for'
      ./features/support/helpers/misc_helpers.rb:33:in `try_for'
      ./features/step_definitions/i2p.rb:5:in `/^I2P is (?:still )?(not )?running$/'
      features/i2p.feature:94:in `Then I2P is running'
    But the network is unplugged                                       # features/step_definitions/common_steps.rb:165
    Then I see a notification that I2P failed to start                 # features/step_definitions/i2p.rb:80
    And I2P is not running                                             # features/step_definitions/i2p.rb:1
      Scenario failed at time 00:39:23

      Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-10376-fix-startup-page-roadmap-test-is-fragile/18/artifact/build-artifacts/00:39:23_I2P_displays_a_notice_when_it_fails_to_start.png

      Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-10376-fix-startup-page-roadmap-test-is-fragile/18/artifact/build-artifacts/00:39:23_I2P_displays_a_notice_when_it_fails_to_start.mkv

00_39_23_I2P_displays_a_notice_when_it_fails_to_start.mkv (138 KB) intrigeri, 05/23/2016 03:09 PM


Related issues

Blocked by Tails - Feature #12264: Reintroduce I2P Confirmed 02/25/2017

History

#1 Updated by intrigeri over 3 years ago

  • Feature Branch set to test/11462-I2P-is-running-is-fragile

#2 Updated by spriver over 2 years ago

Also available in: Atom PDF