We had a build for a single test with an error-free RTS but errors in measurements. Buildstate was green anyways. In this case, buildstate should be set to unstable. There was no error in the build itself. So with other error-free tests you would have appropriate results. Getting an unstable buildstate would let you know that anything did go wrong in single test(s).
What feature do you want to see added?
We had a build for a single test with an error-free RTS but errors in measurements. Buildstate was green anyways. In this case, buildstate should be set to unstable. There was no error in the build itself. So with other error-free tests you would have appropriate results. Getting an unstable buildstate would let you know that anything did go wrong in single test(s).
Upstream changes
No response