You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (Created) (JIRA)" <ji...@apache.org> on 2011/11/11 10:02:51 UTC
[jira] [Created] (COUCHDB-1339) JS CLI Test Suite: use shell trap
to catch dying beam processes during test runs
JS CLI Test Suite: use shell trap to catch dying beam processes during test runs
--------------------------------------------------------------------------------
Key: COUCHDB-1339
URL: https://issues.apache.org/jira/browse/COUCHDB-1339
Project: CouchDB
Issue Type: Improvement
Components: Test Suite
Affects Versions: 1.3
Reporter: Jan Lehnardt
Priority: Blocker
Fix For: 1.3
The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev && utils/run -b and stops it with utils/run -d.
One issue with this is that the CouchDB process might terminate in the background. The shell trap command allows the test suite to act on that accordingly, otherwise the test suite would just freeze.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (COUCHDB-1339) JS CLI Test Suite: use shell trap
to catch dying beam processes during test runs
Posted by "Randall Leeds (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Leeds reassigned COUCHDB-1339:
--------------------------------------
Assignee: Randall Leeds
> JS CLI Test Suite: use shell trap to catch dying beam processes during test runs
> --------------------------------------------------------------------------------
>
> Key: COUCHDB-1339
> URL: https://issues.apache.org/jira/browse/COUCHDB-1339
> Project: CouchDB
> Issue Type: Improvement
> Components: Test Suite
> Affects Versions: 1.3
> Reporter: Jan Lehnardt
> Assignee: Randall Leeds
> Priority: Blocker
> Fix For: 1.3
>
>
> The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev && utils/run -b and stops it with utils/run -d.
> One issue with this is that the CouchDB process might terminate in the background. The shell trap command allows the test suite to act on that accordingly, otherwise the test suite would just freeze.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COUCHDB-1339) JS CLI Test Suite: use shell trap to
catch dying beam processes during test runs
Posted by "Randall Leeds (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Randall Leeds closed COUCHDB-1339.
----------------------------------
Resolution: Fixed
8f0b4e6..2921c78 master -> master
> JS CLI Test Suite: use shell trap to catch dying beam processes during test runs
> --------------------------------------------------------------------------------
>
> Key: COUCHDB-1339
> URL: https://issues.apache.org/jira/browse/COUCHDB-1339
> Project: CouchDB
> Issue Type: Improvement
> Components: Test Suite
> Affects Versions: 1.3
> Reporter: Jan Lehnardt
> Assignee: Randall Leeds
> Priority: Blocker
> Fix For: 1.3
>
>
> The JS CLI test suite that now runs with make check (post 1.2.x master only) starts CouchDB using make dev && utils/run -b and stops it with utils/run -d.
> One issue with this is that the CouchDB process might terminate in the background. The shell trap command allows the test suite to act on that accordingly, otherwise the test suite would just freeze.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira