This is the mail archive of the
mailing list for the Cygwin project.
Re: STC for libapr1 failure
On 2/15/2012 1:20 PM, Corinna Vinschen wrote:
> On Feb 15 13:15, David Rothenberger wrote:
>> On 2/15/2012 12:45 PM, Corinna Vinschen wrote:
>>> On Feb 15 11:39, David Rothenberger wrote:
>>>> On 2/15/2012 7:38 AM, Corinna Vinschen wrote:
>>>>> Did I mention that I hate synchronization problems? Anyway, I think I
>>>>> found the problem. I applied a patch which fixes the problem for me
>>>>> and, surprise!, the flock test still runs fine, too. I've just uploaded
>>>>> a new snapshot. Please give it a try.
>>>> All the procmutex tests pass now! Awesome!
>>>> But... now one of the flock tests is failing. It takes a while to
>>>> extract a STC from the APR test suite because everything is written in
>>>> APR-ese and I have to convert every APR call into the base C library
>>>> calls. I'll work on that over the next day or three.
>>>> The gist of the test that's failing is this:
>>>> * Create a file.
>>>> * Get an exclusive flock on it.
>>>> * Spawn a child process that attempts to get an exclusive, non-blocking
>>>> lock on the file.
>>>> The test is expecting that the child will not be able to get the lock,
>>>> but the child is able to.
>>> Did I really mention that I hate synchronization problems?
>> Yeah, you mentioned it. :-)
>>> Does it fork/exec or does it only exec?
>> Looks like fork/exec. execv to be precise.
>>> I guess I really need the testcase.
>> I'll try to work on that tonight.
> Thanks. Btw., does that testcase fail in 1.7.9 as well?
I'm pretty sure it did. I think all the tests passed the last time I
released this package (2011-09-10), but I might have been testing
against a snapshot. It's hard for me to tell now. If I just install
1.7.9 on my system, things like /bin/ls stop working. The compiled tests
don't run, either.
FYI, the test was passing with 1.7.10 and the 20120214 snapshot. It
didn't start failing until your last snapshot (20120215).
David Rothenberger ---- firstname.lastname@example.org
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple