[
https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990161#comment-12990161
]
Adam Kocoloski commented on COUCHDB-1055:
-----------------------------------------
Hi Noah, that's what I was driving at, but then I read
http://pubs.opengroup.org/onlinepubs/009695399/utilities/sh.html#tag_04_128_16
which said not to make that assumption. *shrugs*, I am far from an expert at
this sort of thing.
> Timing-related failures in 172-os-daemon-errors.t
> -------------------------------------------------
>
> Key: COUCHDB-1055
> URL: https://issues.apache.org/jira/browse/COUCHDB-1055
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Adam Kocoloski
> Assignee: Paul Joseph Davis
> Priority: Minor
> Fix For: 1.2
>
>
> I see quite a few of these on Hudson. Here's one that happened when the
> daemon simply does init:stop(). It seems to happen more often when the
> server is executing two jobs at once.
> # Daemon dies on boot.
> ok 8 - Daemon port is a port.
> ok 9 - Daemon name was set correctly.
> ok 10 - Command name was set correctly.
> ok 11 - Kill command was set.
> not ok 12 - Daemon has been halted.
> ---
> description: "Daemon has been halted."
> found: running
> wanted: halted
> ...
> not ok 13 - Errors have been disabled.
> ---
> description: "Errors have been disabled."
> found: [{1296,674759,844395}]
> wanted: nil
> ...
> not ok 14 - Buffer has been switched off.
> ---
> description: "Buffer has been switched off."
> found: []
> wanted: nil
> ...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
