You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Adam Kocoloski (JIRA)" <ji...@apache.org> on 2011/02/02 22:29:28 UTC
[jira] Created: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
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
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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ 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
[jira] Work stopped: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990164#comment-12990164 ]
Adam Kocoloski commented on COUCHDB-1055:
-----------------------------------------
Linking Jan's report from the mailing list about distcheck failing (and a second vote for sh instead of bash):
http://mail-archives.apache.org/mod_mbox/couchdb-dev/201102.mbox/%3CEE10CDCD-43EA-4AE5-AB35-CDE15051FCF2@apache.org%3E
> 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990151#comment-12990151 ]
Adam Kocoloski commented on COUCHDB-1055:
-----------------------------------------
Yes, the following works:
#! /usr/bin/env sh
Maybe you clear up something about that invocation for me. I get that env is used to make sure we invoke the sh command specified by the user's environment, but is it some sort of POSIX specification that "env" itself is always located in /usr/bin?
> 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Noah Slater (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990154#comment-12990154 ]
Noah Slater commented on COUCHDB-1055:
--------------------------------------
Why are we using `env` for this at all?
Just use the standard location:
/bin/sh
Really, `env` is only supposed to be used for optional binaries.
> 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
[jira] Reopened: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kocoloski reopened COUCHDB-1055:
-------------------------------------
The CI rig didn't like something about those shell scripts. The daemons seem to be dying immediately with
/usr/bin/env: bash -e: No such file or directory
The full report is at [1], but I see this same error if I just execute any of the [234].sh scripts from the command line. Bash is installed at /bin/bash (Ubuntu 10.04.1):
$ bash --version
GNU bash, version 4.1.5(1)-release (x86_64-pc-linux-gnu)
[1]: http://hudson.cloudant.com/job/CouchDB-trunk-R14B01/21/testReport/(root)/test_etap_172_os_daemon_errors_t/Daemon_has_been_halted___3_/
> 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
[jira] Assigned: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Adam Kocoloski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Kocoloski reassigned COUCHDB-1055:
---------------------------------------
Assignee: Paul Joseph Davis
I tried timing 172-os-daemon-errors.2.es on the CI rig. It took about 230 ms for each invocation except the first one, which took 910 ms.
Paul, do you think it would make sense to replace these escript test daemons with their sh equivalents? The startup costs would be much smaller (~10 ms in my timings) and probably less variable.
> 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
[jira] Closed: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis closed COUCHDB-1055.
--------------------------------------
Resolution: Fixed
Good idea.
Updated in 1066704
> 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
[jira] Work started: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on COUCHDB-1055 started 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Noah Slater (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990175#comment-12990175 ]
Noah Slater commented on COUCHDB-1055:
--------------------------------------
Crap, I didn't even read the thread properly. We definitely shouldn't be using `bash` at all. As your resident portability geek, I am going to upgrade my suggestion to a request. Hehe.
Please change the line to:
#!/bin/sh -e
This should be the case for every single shell script in our codebase.
> 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989949#comment-12989949 ]
Paul Joseph Davis commented on COUCHDB-1055:
--------------------------------------------
Try /use/bin/env sh
> 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
[jira] Commented: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990163#comment-12990163 ]
Paul Joseph Davis commented on COUCHDB-1055:
--------------------------------------------
@Adam
Not really a convention. I've heard of platforms that but env in /bin vs /usr/bin and what not.
@Noah
Just out of habit.
@Adam
Me neither. Just seems to work most of the time.
> 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
[jira] Resolved: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis resolved COUCHDB-1055.
----------------------------------------
Resolution: Fixed
Shebang lines are fixed. Distcheck is fixed. Build system is happy again.
> 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
[jira] Work stopped: (COUCHDB-1055) Timing-related failures in
172-os-daemon-errors.t
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ 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