[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] What is our current bug state?

From: Frank Nicholas
Subject: Re: [gpsd-dev] What is our current bug state?
Date: Mon, 2 Feb 2015 14:15:28 -0500

On Feb 2, 2015, at 12:35 PM, Eric S. Raymond <address@hidden> wrote:

Please test head with WRITE_PAD and CLOSE_DELAY zeroed.  It looks
now as though O_NONBLOCK may have been the culprit behind that problem too.

Current behavior is to open with O_NOBLOCK, set CLOCAL, then use fcntl to
clear O_NONBLOCK.  This seems to work fine even if no VTIME is set!

Mac OS X, 10.10 (Yosemite), MacBook Pro, Intel Core i7-4850HQ (quad core, w/hyper-threading)

I did a ‘git pull’.  I’m not sure how to see what revision it was, but the latest commit was “ef39b1cd848a006751b1d30c931056a5790e3116”.

I zeroed out the WRITE_PAD & CLOSE_DELAY, and had mostly failure:
Regression test FAILED: 87 errors in 89 tests total (0 not found).
-n Elapsed time: 

I set the WRITE_PAD & CLOSE_DELAY back to how they were (.03 & 1) for OS X, and it passed:
Regression test successful: no errors in 89 tests (0 not found).
-n Elapsed time: 

In the failed tests, it appears the the input file being tested was spit out in the terminal window.  Is that intentional if a test fails, or is it a byproduct of a failed test?

Any additional information you would like?  Any other testing you want performed?  The Apple developer tools allow me to turn off cores on the fly, if we think this might be related to SMP.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]