Opened 8 years ago

Closed 8 years ago

#1795 closed defect (duplicate)

xfrin lettuce test fails

Reported by: jinmei Owned by:
Priority: medium Milestone: Year 3 Task Backlog
Component: xfrin Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by jinmei)

This one always fails. Not sure why it doesn't happen for others.

    When I send bind10 the command Xfrin retransfer example.org IN 127.0.0.1 47807                               # features/terrain/bind10_control.py:299
    Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR    Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE                 # features/terrain/steps.py:34
    Traceback (most recent call last):
      File "/Library/Python/2.7/site-packages/lettuce/core.py", line 117, in __call__
        ret = self.function(self.step, *args, **kw)
      File "/Users/jinmei/src/isc/git/bind10/tests/lettuce/features/terrain/steps.py", line 49, in wait_for_message
        (found, line) = world.processes.wait_for_stderr_str(process_name, strings, new)
      File "/Users/jinmei/src/isc/git/bind10/tests/lettuce/features/terrain/terrain.py", line 317, in wait_for_stderr_str
        only_new)
      File "/Users/jinmei/src/isc/git/bind10/tests/lettuce/features/terrain/terrain.py", line 220, in wait_for_stderr_str
        strings, only_new)
      File "/Users/jinmei/src/isc/git/bind10/tests/lettuce/features/terrain/terrain.py", line 205, in _wait_for_output_str
        assert False, "Timeout waiting for process output: " + str(strings)
    AssertionError: Timeout waiting for process output: [u'XFRIN_TRANSFER_SUCCESS', u'XFRIN_XFR_PROCESS_FAILURE']

lettuce/output files were attached (they are big, so archived)

Subtickets

Attachments (1)

log.tgz (134.3 KB) - added by jinmei 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by jinmei

comment:1 Changed 8 years ago by jinmei

  • Description modified (diff)

comment:2 Changed 8 years ago by jelte

hey that log looks remarkably similar to the 'two instance' test failure. And both look like something is looping over an error and bringing down the entire system.

comment:3 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 4

comment:4 Changed 8 years ago by jinmei

#1772 also fixed the issue described of this ticket. Closing.

comment:5 Changed 8 years ago by jinmei

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.