-
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
[wasm] WBT: Blazor tests on windows failing with Failed to bind to address
for random ports
#92910
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError BlobTagging this for KnownBuildError in case it's happening consistently and we need to fix this in 8.0. {
"ErrorMessage": "",
"BuildRetry": false,
"ErrorPattern": "Wasm\.Build\.Tests.*System\.IO\.IOException: Failed to bind to address http://127\.0\.0\.1:(?!5000)",
"ExcludeConsoleLog": false
} Reproduction Steps
Known Issue Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
@missymessa Any idea why this is not getting picked up for known-build-error analysis? |
@maraf Looking at the logs, the same port number is used in one of the earlier tests, but even if that process is still running the devserver shouldn't have picked a port still in use. Seems like a devserver issue? |
@radical it wasn't picked up because it had escaping problems, you can notice this because the json message was in red, like this: {
"ErrorPattern": "Wasm\.Build\.Tests.*System\.IO\.IOException: Failed to bind to address http://127\.0\.0\.1:(?!5000)"
} I fixed the escaping and now the validation was able to run, but I noticed that your regex was trying to look into multiple lines, this feature is not available for known issues, the error needs to be a single line, also the validation returned a backtracking error, all this needs to be fixed in order than known issues can work let me know if you need help with any of this |
Oh, I was basing this on the doc:
The If that isn't supported then what is the recommended way to identify failure messages that are not unique. For example |
Unfortunately, there is not a lot that we can suggest on these cases, if this is narrow to a specific test name you can use the test name, otherwise the only option is try to identify an error line that is unique to your issue. we provide a little bit more information about why the multiline is not supported of this issue: dotnet/arcade#13253 |
Maybe allowing matching against the helix item name, or maybe two single line patterns to match? That should be cheaper than a multiline regex search over a big text file. |
does it not happen anymore ? Or the filter doesn't work ? |
Commenting to save the current state (yes, it did happen after the question): Summary
|
Reproduction Steps
browser-wasm linux Release WasmBuildTests
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎⚠️ Build internal information not found. This may happen if your build is too old. Please use a build that is no older than two weeks. If the problem persists, contact .NET Engineering Services Team and share this issue.
Result validation:
Validation performed at: 10/17/2023 1:46:13 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: