-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Infrequent flake in golang_integration_test
#29496
Comments
cc @doujiang24 |
Okay, I'll look further and keep an eye on it, thanks~ |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
Still happening (link) |
fix #31654 and #29496 Thanks @spacewander for founding this race: envoyGoRequestSemaDec may be invoked eariler than r.sema.Wait, then, there is no one to resume the r.sema.Wait. Commit Message: Additional Description: Risk Level: Testing: Docs Changes: Release Notes: Platform Specific Features: Fixes: #31654, #29496 Signed-off-by: doujiang24 <doujiang24@gmail.com>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
…roxy#32081) fix envoyproxy#31654 and envoyproxy#29496 Thanks @spacewander for founding this race: envoyGoRequestSemaDec may be invoked eariler than r.sema.Wait, then, there is no one to resume the r.sema.Wait. Commit Message: Additional Description: Risk Level: Testing: Docs Changes: Release Notes: Platform Specific Features: Fixes: envoyproxy#31654, envoyproxy#29496 Signed-off-by: doujiang24 <doujiang24@gmail.com>
This doesnt seem to happen very often but its persisting
Ive mentioned it a few times on the golang slack channel but raising here as i think we need to look further
example fail:
https://dev.azure.com/cncf/envoy/_build/results?buildId=148510&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=8a34f9ed-4946-5fcf-7cd6-99c93070884d&l=1473
The text was updated successfully, but these errors were encountered: