> Another problem with the dashboard API check in its current form
> is wasted lab resources [1]. Perhaps someone from the dashboard
> team could assist David there.
Ilya, when we asked David to enable this Jenkins job on all PRs, the first thing we did was to check with David and ensure we had enough lab resources to cope with running this for all PRs.
That said, we'll provide all support needed to improve the build workflow (either by saving workspaces/using pipelines/running from packages/whatever).
Coming back to the topic of the stability of the API test, this is the 60-day chart of build statuses for 'make check' vs. Ceph API test.
As you may see, the failure rate & build count is lower for API test job, and that considering that build failures at "make check" will result in API test failures.
While "make check" errors are usually more informative for the PR author, API test failures can also be useful for detecting & improving Ceph-wide issues (as Kefu did recently:
https://github.com/ceph/ceph/pull/35871).
Kind Regards,
Ernesto