mcobbett exit immediately when all tests done

[techcobweb]

Why ?

While investigating galasa-dev/projectmanagement#2009 I noted that the CLI tool didn't exit the moment the last test completed.
It used to but at some point it stopped doing that.

It turns out that 2 timer services were being created. One thread went to sleep on one, and the other thread woke up on the other. So the interrupt event never woke the sleeping thread.

Solution: Use a single sleep service, and separate the sleeper service from the time service so it's less likely in the future.

Also, using the golang select... and time.After(delay) is the recommended way of doing this stuff as of Golang 1.23. What I've coded does work, but prior to 1.23 may result in a timer resource leakage.

We need to uplift the golang requirement to 1.23 next to avoid any resource leakage.

• Use timer service to wake up outer loop
• run status was never being reported properly for local runs. Only result was being copied over into the reported structure.
• Separated out the time service from the sleeper service.

[galasa-team]

Build failed, see http://localhost:8001/api/v1/namespaces/tekton-pipelines/services/tekton-dashboard:http/proxy/#/namespaces/galasa-build/pipelineruns/repo-cli-pr-298-x7c6n for details. If you are unable to do so, please contact a member of the Galasa team.

[galasa-team]

Build failed, see http://localhost:8001/api/v1/namespaces/tekton-pipelines/services/tekton-dashboard:http/proxy/#/namespaces/galasa-build/pipelineruns/repo-cli-pr-298-89bs2 for details. If you are unable to do so, please contact a member of the Galasa team.

[galasa-team]

Build failed, see http://localhost:8001/api/v1/namespaces/tekton-pipelines/services/tekton-dashboard:http/proxy/#/namespaces/galasa-build/pipelineruns/repo-cli-pr-298-gbl7m for details. If you are unable to do so, please contact a member of the Galasa team.

[galasa-team]

Build successful

[galasa-team]

Build successful

[galasa-team]

Build successful