gpsd-dev
[Top][All Lists]
Advanced

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

Re: b32ff1a86 Breaks OSX and FreeBSD


From: Bernd Zeimetz
Subject: Re: b32ff1a86 Breaks OSX and FreeBSD
Date: Sat, 21 Dec 2019 21:45:27 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0


On 12/21/19 8:37 PM, Hal Murray wrote:
> 
>> will be interesting to find it as it is not easy reproducible.
> 
> Have you tried WRITE_PAD=0.0 on NetBSD or FreeBSD?

I've tried several variants of 0 <= WRITE_PAD <= 1 on FreeBSD, none with
a reproducible result.
Also I completely fail to understand why this is needed at all, it must
be a workaround for some bug, where ever that is.

> sys netbsd8 platform NetBSD-8.1-amd64-x86_64-64bit-ELF: WRITE_PAD = 0.00000
> Regression test FAILED: 69 errors in 135 tests total (0 not found).
> scons: *** [gps-regress] Error 69
> 13 Test timed out: maybe increase WRITE_PAD (= 0.0)
> 
> I just noticed this:
> -$GPGSA,A,3,29,11,1,3,28,,,,,,,,5.2,3.1,3.3*34
> +$GPGSA,A,3,1,11,29,3,28,,,,,,,,5.2,3.1,3.3*34

I've seen similar things, changes in the order of messages or parts of
the message.

> That was the only error in that file.
> That's with test/daemon/superstar2.log
> It's at least somewhat reproducable and takes a long time using the CPU.
> 
> In case it matters:
> model name      : Intel(R) Atom(TM) CPU D2500   @ 1.86GHz
> 
> -------
> 
> sys freebsd12 platform FreeBSD-12.1-RELEASE-p1-amd64-64bit-ELF: WRITE_PAD = 
> 0.00
> Regression test FAILED: 89 errors in 135 tests total (0 not found).
> No timeouts.

Gary gave FreeBSd a try yesterday and was not able to get a single
failure. No idea on which hardware, but I'd assume on some fast desktop
machine.


So I guess BSD and a slow machine is necessary.

By gitlab-runner is running in a kvm instance on a not-so-recent server
hardware with various VMs, so speed depends on the work the other VMs do..

I think I can get some slow and old firewall hardware and run it in the
datacenter and give people access to it - if the issue is reproducible.
I'll figure it out after Christmas.


-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F



reply via email to

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