On Mon, Feb 17, 2025 at 01:23:52AM -0800, Hal Murray wrote: > > What's interesting about the 3? Are some of the other tests also testing > plain old asciidoc?
It's an asciidoc implementation written in python 3, instead of ruby. We're only testing that the asciidoc program runs without errors. We're not checking that it produces the expected output. > James' fix worked so things are back to normal. Do we want to cleanup the > CI stuff before or after the release? I think they're orthogonal. > There are 2 other .gitlab-ci files. They get included by .gitlab-ci.yml > but they don't get used, at least by the normal CI process that I pay > attention to. > .gitlab-opttest-ci.yml These jobs are only run when the source is "schedule" (eg, the weekly scheduled run). If we think the option testing is valuable, then we can run it on every commit. I'm not sure why we have the "make-tarball" CI target. We don't use that tarball for anything. > .gitlab-docker-ci.yml These jobs also only run when the source is "schedule". This is fine for docker image creation since we need the images updated periodically, not on every commit. Thanks, -Matt _______________________________________________ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/listinfo/devel
