Nigel Jones

Investigated external runners -- but hit issues with KinD. commented in actions-runner-controller discussion. Reverted to debugging github runners. The following fragment assisted with debugging (see https://github.com/lhotari/action-upterm for more info): ```...

SUCCESSFUL test run -> https://github.com/planetf1/cts/actions/runs/3708502295 - ie tasks completed as successful results are attached to the job. WIll elaborate the job to do some basic checks of the results.

Example output I'm experimenting with This is based on positive/negative evidence counts in the details cts results ie: ``` ➜ graph ./cts-analyze.py Metadata sharing MANDATORY_PROFILE CONFORMANT_FULL_SUPPORT [ 71657 / 0...

Added checks into latest pipeline. Set default container to 'latest' Added schedule, daily

I have reverted the doubling of the retry count used during CTS after seeing run-times on the CTS automation exceed 6 hours. Analysis of the cts execution is needed, but...

I'm proposing to move my repo under odpi. Whilst no doubt we can make improvements, refactor, it's a starting point, and moving it will make it easier for others to...

Having backed of the timer increase, CTS is now running in 4-4.5 hours. will leave like this

Is the gradle log better? Can we close this - or are there specific things you want to add?

Adding users in CODEOWNERS is good practice regardless, as it should help to automatically assign reviewers. It's worth ensuring >1 owner on each area. Having 2 reviewers is nice, and...

I don't seem to be able to start docker at all. Not only do I get the message at startup, but also if trying to start docker later  I...