[gpsd-dev] ✘GPS roll over and regressions

[Gary E. Miller]

Yo All!

After three days, I have to agree with Eric on just rebuilding the
regressions.  I looked hard at the bu303 (SiRF II) regressions.  Nothing
in there (leap seconds, UTC, year, etc.) to help disambiguate GPS
epochs.  Anyone still using them should just spend $5 and update to a
new u-blox M8030.

So I just pushed updates to the bu303 regressions.

That leaves:

"test/daemon/greis-binary.log"
"test/daemon/greis-raw-2m.log"
"test/daemon/greis-reset.log"
"test/daemon/greis-test2.log"

On GREIS the time went from: "2017-12-16T03:35:09.750Z" to
"2037-08-01T03:35:09.750Z".  If, after looking hard, that is the
only problem, then I'll just rebuild those regressions too.

"test/daemon/sirfstarv.log"

This one is weird.  Time bounces from "1902-07-17T15:25:43.000Z" to
"2019-01-06T21:54:00.000Z".  No ideas yet, but it needs some fixing.

"test/daemon/ublox-sirf1.log"

The ublox-sirf1 is from 2005.  The firmware is from 2000.  Another one
that should be a cat toy.  It does contain a UTC 4 digit year, but
putting that info into all the other places that just uses GPS weeks and
TOW turned out to be a PITA.  I'll leave it to last and will likely just
rebuild the regression.

Luckily the insistance on GPZDA in NMEA made those regressions hold up
fine.  All the other well tested drivers also worked fine.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin

pgpSYd7vA9keY.pgp
Description: OpenPGP digital signature