Unstable java-groovy test project for Secure SAST
Summary
Our spotbugs-sast
job will occasionally fail for the https://gitlab.com/gitlab-org/security-products/tests/java-groovy project due to some crashing of the gradle daemon. This seems inconsistent and not easily reproducible. Usually this can fixed by restarting the job, for example: https://gitlab.com/gitlab-org/security-products/tests/java-groovy/-/jobs/749009924
Steps to reproduce
?
Example Project
- https://gitlab.com/gitlab-org/security-products/tests/java-groovy/-/jobs/747094014
- https://gitlab.com/gitlab-org/security-products/tests/java-groovy/-/jobs/741345016
What is the current bug behavior?
Job fails due to gradle daemon crashing
What is the expected correct behavior?
Job succeeds
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Possible fixes
- Short-term: Add
retry
totests/java-groovy
spotbugs-sast
job - Long-term: Debug and avoid gradle daemon failures
Edited by Lucas Charles