On Sat, Sep 07, 2024 at 05:43:32PM -0700, Hal Murray via devel wrote:
>
> Thanks
>
> James said:
> >It is one of many jobs set up to fail withou fanfare. Nobody was
> >checking up on them on the pipelines tab at GitLab.
>
> Why do we have those jobs?
I think the idea at the time was th
On Sat, Sep 07, 2024 at 04:14:52PM -0500, Dan Drown via devel wrote:
>Ubuntu 16.04 is pretty old, does it need to be supported?
Nope. I've removed this CI target.
https://gitlab.com/NTPsec/ntpsec/-/commit/5af01fe36a66b60496fcdf7bcfc31334370cff1b
Cheers,
-Matt
__
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
Does #ifdef work on functions? I thought not, but the old code looks like
its doing that.
It only works when the apparent functions are macros. The preprocessor
knows nothing about functions.
On Sat, 7 Sep 2024, Hal Murray via devel wrote:
Gary said:
>> >It is one of many jobs set up to fail withou fanfare. Nobody was
>> >checking up on them on the pipelines tab at GitLab.
>> Why do we have those jobs?
> To test commits that they don't break the build.
Right. But if they fail silently nobody notices that something is bro
Yo Hal!
On Sat, 07 Sep 2024 17:43:32 -0700
Hal Murray via devel wrote:
> James said:
> >It is one of many jobs set up to fail withou fanfare. Nobody was
> >checking up on them on the pipelines tab at GitLab.
>
> Why do we have those jobs?
To test commits that they don't break the bu
