BIND 10 #2790: Lettuce tests timing & missed messages
BIND 10 Development
do-not-reply at isc.org
Mon Mar 4 00:18:11 UTC 2013
#2790: Lettuce tests timing & missed messages
-------------------------------------+-------------------------------------
Reporter: vorner | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: Unclassified | Tasks
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by muks):
Replying to [ticket:2790 vorner]:
> The lettuce tests fail quite often, usually by waiting for some message
to appear. However, the message seems to present in the log output file.
Also, it didn't seem to have any garbage around, as suggested elsewhere.
I don't know what this particular case is. But many lettuce features have
statements that wait for a "next" log message (after that point in time).
The message ID may have been logged before, but it waits for a new one.
--
Ticket URL: <https://bind10.isc.org/ticket/2790#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list