-
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
[browser] Connection refused in 127.0.0.1 #104349
Comments
Tagging subscribers to 'arch-wasm': @lewing |
cc @ilonatommy |
I think this is just slow helix machine. It usually recovers from it eventually. |
Should we set BuildRetry to true? |
Good idea. I wonder if we could somehow detect re-run like that and eventually enable more logging. Does CI set some env variable ? |
That's a great question for which I don't have an answer. @AlitzelMendez is it possible to detect that a CI run was triggered a second time due to |
This is kind of "catch all" filter and it was hiding #108175 and maybe more. |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=875122
Build error leg or test failing:
browser-wasm linux Release WasmBuildTests
Error Message
browser-wasm linux Release WasmBuildTests
Output (expand)
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=875122
Error message validated:
[[wasm test-browser] Connection refused
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/21/2024 9:41:24 PM UTC
Report
Summary
Report
Summary
The text was updated successfully, but these errors were encountered: