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

Paul Joseph Davis resolved COUCHDB-515.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11

I fixed this as part of the work on getting buildbot up and running and didn't 
think to backport it. Its a bug in the test not what's being tested so it 
doesn't concern me too much. Though it does point at interestingness of Erlang 
scheduling being different in different scenarios. It wasn't even noticed until 
trying to run the tests in coverage mode on an Ubuntu VM.

Here's the diff:

http://svn.apache.org/viewvc/couchdb/trunk/test/etap/040-util.t?r1=819263&r2=819341

There was an odd race condition when the terminate_linked call executed before 
the linked process started. This patch just adds a receive for a message from 
the new PID before executing terminate_linked.

There's also another patch that updates the plan count to 11, so this will 
still break prove (because it runs one more test than expected).

>  040-util fail on freebsd 7.2 
> ------------------------------
>
>                 Key: COUCHDB-515
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-515
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 0.10
>         Environment: freebsd 7.2, erlang R13B02, 
>            Reporter: Benoit Chesneau
>             Fix For: 0.11
>
>
> make check block on 040-util step 4 however http tests works and it don't 
> seem to affect work on it (like friendpaste). prove -v display nothing more, 
> the tests just block on it and I had to kill it (ctrl-c).
> uname -a : 
> FreeBSD node0.somedomain.com 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed 
> Jun 24 00:14:35 UTC 2009     
> [email protected]:/usr/obj/usr/src/sys/GENERIC  amd64
> erlang :
> Erlang R13B02 (erts-5.7.3) [source] [64-bit] [smp:2:2] [rq:2] 
> [async-threads:0] [hipe] [kernel-poll:false]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to