You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2011/02/03 01:28:28 UTC

[jira] Work stopped: (COUCHDB-1055) Timing-related failures in 172-os-daemon-errors.t

     [ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on COUCHDB-1055 stopped by Paul Joseph Davis.

> 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