Re: CI stuff failing

2025-02-18 Thread Hal Murray via devel
matthew.sel...@twosigma.com said: > Let's remove this CI target. There's no need to test a specific version > of AsciiDoc 3 on every commit. It was working yesterday after James' fix. It was broken a few minutes ago. So I took your suggestion and commented it out. -- These are my opinions

Re: CI stuff failing

2025-02-17 Thread Hal Murray via devel
matthew.sel...@twosigma.com said: > Yes. You can manually run a pipeline manually at > https://gitlab.com/NTPsec/ntpsec/-/pipelines That's the normal CI pipeline collection of tests. Is there an option to run the scheduled tests that I didn't see? > What's the advantage to running a pipelin

Re: CI stuff failing

2025-02-17 Thread Matt Selsky via devel
On Mon, Feb 17, 2025 at 03:16:14PM -0800, Hal Murray wrote: > Thanks again. Is there a way to manually kick them off? Or get them to > run an hour to 3 after a commit? Yes. You can manually run a pipeline manually at https://gitlab.com/NTPsec/ntpsec/-/pipelines What's the advantage to runnin

Re: CI stuff failing

2025-02-17 Thread Hal Murray via devel
matthew.sel...@twosigma.com said: > 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. Thanks. Yup. Testing documentation is an interesting problem

Re: CI stuff failing

2025-02-17 Thread Matt Selsky via devel
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 error

Re: CI stuff failing

2025-02-17 Thread Hal Murray via devel
matthew.sel...@twosigma.com said: > Let's remove this CI target. There's no need to test a specific version > of AsciiDoc 3 on every commit. What's interesting about the 3? Are some of the other tests also testing plain old asciidoc? James' fix worked so things are back to normal. Do we wa

Re: CI stuff failing

2025-02-17 Thread James Browning via devel
On Feb 16, 2025 23:36, Matt Selsky via devel wrote:On Sun, Feb 16, 2025 at 11:16:28PM -0800, Hal Murray via devel wrote: > I poked around a bit and didn't find anything with version numbers.  There > was a latest. asciidoc3.org's blog mentions a complete revamp of their website. See https:

Re: CI stuff failing

2025-02-16 Thread Matt Selsky via devel
On Sun, Feb 16, 2025 at 11:16:28PM -0800, Hal Murray via devel wrote: > I poked around a bit and didn't find anything with version numbers. There > was a latest. asciidoc3.org's blog mentions a complete revamp of their website. See https://asciidoc3.org/blog-news/2025/ Let's remove this CI ta

CI stuff failing

2025-02-16 Thread Hal Murray via devel
AsciiDoc-3-Fedora : $ wget https://asciidoc3.org/asciidoc3-3.2.3.tar.gz [0] Downloading 'https://asciidoc3.org/asciidoc3-3.2.3.tar.gz' ... HTTP ERROR response 404 [https://asciidoc3.org/asciidoc3-3.2.3.tar.gz] I poked around a bit and didn't find anything with version numbers. There was a lates