-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
[exporter/clickhouse] Integration test failing due to time out #32275
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This may just be a test issue, but I'm labelling as a bug until it's been investigated 👍 |
I might have seen this even when running locally. The tests do pass, this is likely a one-off error with a container failing to start in time. Is this the first/only run for the CI? @crobert-1 Any thoughts on how we could make this more robust? @Frapschen |
That's the first run on that PR. I think I might have seen it before, but I don't definitively remember. I'm aware of general stability issues around
Just a couple initial thoughts. |
This was my interpretation as well. It's what usually happens when docker integration tests fail. If the CI has a shared image cache we could try using an exact image hash instead of always pulling the latest for that tag. Quickest workaround for now is to re-run and see if docker is quicker. Maybe we can shorten the timeout for |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Should be investigated with #32530 As suggested in a comment over there these could probably be fixed in a single PR |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Similar to #32530, still needs investigation |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
exporter/clickhouse
Describe the issue you're reporting
CI/CD link here.
Failure output:
The text was updated successfully, but these errors were encountered: