Add switch for running Sonobuoy tests in parallel#1117
Conversation
847d773 to
de7a67e
Compare
See SovereignCloudStack/standards#1117 Signed-off-by: Kurt Garloff <kurt@garloff.de>
|
OK, on my CiaB (8-core) test with a 3+3 cluster, the |
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
as decided by SIG Standardization/Certification on 2026-03-12 Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
de7a67e to
a7056f1
Compare
There was a problem hiding this comment.
IMHO this could be an ideal test ballon for auto-generated tests. Would have to be checked manually as well of course. I tried this with Claude an attach the result for future reference. I didn't test these tests myself.
scs-compliance-check-test.yaml
scs_compliance_check_test.py
report.yaml
|
I think is goes without saying that feeding our code to Claude is not something I appreciate. The test code it produced is 885 lines of boilerplate code that would need maintenance, for instance, it checks whether all command-line options are documented in the usage output, but the list of options is hard-coded, so it's no use at all. I can't stress enough how I oppose this. |
Many people at the SCS hackathon observed that Sonobuoy took a lot of time. Having it run its tests in parallel might help that.