BIND 10 #2625: lettuce timing failure for starting cmdctl for In-memory datasource backed by sqlite3
BIND 10 Development
do-not-reply at isc.org
Thu Jan 10 17:01:28 UTC 2013
#2625: lettuce timing failure for starting cmdctl for In-memory datasource backed
by sqlite3
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: | Status: new
defect | Milestone: New Tasks
Priority: low | Keywords:
Component: | Sensitive: 0
Unclassified | Sub-Project: Core
CVSS Scoring: | Estimated Difficulty: 0
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Lettuce failure on CentOS 5.8 with python 3.3.0. This does not happen
every time, but I saw it three times out of six runs. The stderr output
shows that was not started yet. I guess it should wait a little longer.
Scenario: 2. In-memory datasource backed by sqlite3
features/inmemory_over_sqlite3.feature:14
...
And wait for master stderr message CMDCTL_STARTED
# features/terrain/steps.py:34
...
AssertionError: Timeout waiting for process output:
[u'CMDCTL_STARTED']
--
Ticket URL: <https://bind10.isc.org/ticket/2625>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list