gpsd-dev
[Top][All Lists]
Advanced

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

Re: ✘ Release blockers?


From: Bernd Zeimetz
Subject: Re: ✘ Release blockers?
Date: Tue, 24 Dec 2019 18:48:14 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0


On 12/24/19 4:17 PM, Greg Troxel wrote:

> I removed -o -t from SConstruct:
> 
> @@ -2268,7 +2268,7 @@ else:
>      for gps_name, gps_log in zip(gps_names, gps_logs):
>          gps_tests.append(Utility(
>              'gps-regress-' + gps_name, gps_herald,
> -            '$SRCDIR/regress-driver -q -o -t $REGRESSOPTS ' + gps_log))
> +            '$SRCDIR/regress-driver -q $REGRESSOPTS ' + gps_log))
>      gps_regress = env.Alias('gps-regress', gps_tests)
>  
>      # Run the passthrough log in all transport modes for better coverage
> 
> and am rerunning.  (I'm not sure if that's right, and what the
> recommended way to switch between tcp and pty for input is.)
> This also had a faliuer, but it looks like the usual too-low-WRITE_PAD
> type.

-o -t uses tcp
-o -u uses udp
no -o at all -> pty.

There is no option in gpsfake to force pty usage.


-- 
 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]