CI stuff failing
Matt Selsky
Matthew.Selsky at twosigma.com
Tue Feb 18 04:50:21 UTC 2025
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 running a pipeline an hour or 3 after a commit instead of at commit time? Or even at MR creation time?
> There seems to be a pattern of running standard and with-refclocks on
> various platforms. What's the overhead of of a test? Would it be
> appropriate to make a mini option tester to be run on each platform?
Each CI job costs a given number of CI minutes and I believe we hae 50K minutes/month with our GitLab.com OSS subscription
I'm not super familiar with the internals of the option tester script. The https://docs.gitlab.com/ci/yaml/#parallelmatrix keyword may make it easier to see what's different between each of the options and which platforms we want to test those options against.
Can you explain a bit more about the goal of the options tester and the key things you want it to test?
Thanks,
-Matt
More information about the devel
mailing list