Scheduled integration test pipeline failing on sast project
Summary
Our master
branch for security-products/sast
is failing during the integration tests. We should investigate the failure and resolve it.
First failure was on September 4th: https://gitlab.com/gitlab-org/security-products/sast/pipelines/80375858
Steps to reproduce
Set up a scheduled pipeline for master
and see failure; i.e. https://gitlab.com/gitlab-org/security-products/sast/pipelines/83087222
Example Project
https://gitlab.com/gitlab-org/security-products/sast
What is the current bug behavior?
test
fails
What is the expected correct behavior?
test
should not fail
Relevant logs and/or screenshots
What appears to be the relevant error from the log:
* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)