We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Periodically in CI, on the all tests, the test will hang/timeout on a package. It is commonly Grafana or Prometheus stack that the timeout occurs on. Generally Pending pods can be observed in the debug output, ex: https://github.com/defenseunicorns/uds-core/actions/runs/8268437284/job/22621379639?pr=210#step:9:55
all
We should identify where/why this is happening to make our CI more robust and less prone to flaky failures.
A number of suspicions have been proposed but so far debug hasn't yielded anything concrete:
The text was updated successfully, but these errors were encountered:
fix: use updated k3s (#426)
1da1c49
## Description Testing CI with upgraded k3s ## Related Issue Fixes #253 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md)(https://github.com/defenseunicorns/uds-template-capability/blob/main/CONTRIBUTING.md#submitting-a-pull-request) followed
a878697
rjferguson21
Successfully merging a pull request may close this issue.
Describe what should be investigated or refactored
Periodically in CI, on the
all
tests, the test will hang/timeout on a package. It is commonly Grafana or Prometheus stack that the timeout occurs on. Generally Pending pods can be observed in the debug output, ex: https://github.com/defenseunicorns/uds-core/actions/runs/8268437284/job/22621379639?pr=210#step:9:55We should identify where/why this is happening to make our CI more robust and less prone to flaky failures.
Additional context
A number of suspicions have been proposed but so far debug hasn't yielded anything concrete:
The text was updated successfully, but these errors were encountered: