Nigel Jones

Closing as not planned

removing maven tag, as will address this only for gradle

Tests are running viable. With no discussion in this issue I am going to close - we can open issues as needed for specific changes

See also https://github.blog/2023-03-28-introducing-self-service-sboms/ & referenced actions

This is still occuring

A few simple things we could check - number of tests failed is 0 - number of tests successful is > ???? (current number? just big? could be checked in)...

An initial version of this is now being tested at https://github.com/planetf1/cts Still debugging, but expected: The github action will * run 2 parallel jobs - for inmem & graph *...

After 4.5 hours, the CTS is still running (even at the minimum size (5 vs 1) - even in memory (and graph takes longer) -> https://github.com/planetf1/cts/actions/runs/3695246683/jobs/6257391400 I set the job...

I usually run on a 3-6 x 16GB cluster ... Though often multiple instances in parallel (all the charts) I have run locally in around a 6-8GB but indeed this...

Two projects to setup github actions runners on a k8s cluster: https://github.com/evryfs/github-actions-runner-operator https://github.com/actions-runner-controller/actions-runner-controller The latter is being taken over by github for native support https://github.com/actions/actions-runner-controller/discussions/2072