[Top][All Lists]

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

Re: [gpsd-dev] Please test with WRITE_PAD zeroed

From: Hal Murray
Subject: Re: [gpsd-dev] Please test with WRITE_PAD zeroed
Date: Sun, 15 Feb 2015 02:31:29 -0800

> One of the solutions implies that it may in fact be possible to do away with
> WRITE_PAD entirely; the counter-evidence was from running a atale version of
> a shared library.

On Linux, WRITE_PAD is already 0.  I haven't seen any lost-packet troubles.

On NetBSD, your timeout trap goes off on one or two tests of the standard 

:; ./gpsfake -T; ./gpsctl -R 2>/dev/null; ./regress-driver test/daemon/*.log
sys netbsd6 platform NetBSD-6.1.5-i386-32bit-ELF: WRITE_PAD = 0.00000

Processing test/daemon/haicom-305N.log
Test timed out: increase WRITE_PAD = 0.0

check-0.log:Regression test FAILED: 2 errors in 89 tests total (0 not found).
check-1.log:Regression test FAILED: 1 errors in 89 tests total (0 not found).

On FreeBSD, it goes off most of the time.  udp-test.log and tcp-test.log 
work, or at least they did the few times I tried them.

You might look into bypassing the diff step if the data collection step 
returns an error code.  That would improve the signal-noise ratio in the 
printout when chasing things like this.

Do you expect it to use 100% of a CPU while waiting?

92940 murray      1 103    0 16092K  7656K CPU1    1   0:51 100.00% python


I have another NetBSD box that always has troubles with timing delays, even 
in SLOW mode.  It's 64 bit Atom (2x CPU) vs 32 bit Celeron above.  (I'm not 
claiming that is important.)

sys netbsd6 platform NetBSD-6.1.5-amd64-x86_64-64bit-ELF: WRITE_PAD = 0.10000

Without SLOW mode:
WRITE_PAD of 0.05 is not enough.
WRITE_PAD of 0.1 works so far.

For the record, as long as I'm testing things...

Processing test/daemon/superstar2.log
Processing test/daemon/tcp-test.log
gpsd:ERROR: TCP device open error can't connect to host/port pair.
gpsd:ERROR: tcp:// device activation failed.
Processing test/daemon/tcp-torture.log

Processing test/daemon/tcp-test.log
gpsfake: unknown internal I/O error [Errno 48] Address already in use
(snip diff output)
Processing test/daemon/udp-test.log

These are my opinions.  I hate spam.

reply via email to

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