Open radical opened 7 months ago
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Author: | radical |
---|---|
Assignees: | - |
Labels: | `arch-wasm`, `blocking-clean-ci`, `Known Build Error` |
Milestone: | - |
@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
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,
Oh, I was basing this on the doc:
We recommend you test your regular expression, to do it you can use [regex101 tester](https://regex101.com/) (choose .NET (C#) flavor) with the following regex options:
Single line
Insentitive
No backtracking
The single line
here would mean that .
would match newlines also, even according to that website.
If that isn't supported then what is the recommended way to identify failure messages that are not unique. For example System.IO.IOException: Failed to bind to address
can match lots of test failures but the issue is specifically about this failure in Wasm.Build.Tests
. Without the multi-line regex, how do I narrow down the match?
If that isn't supported then what is the recommended way to identify failure messages that are not unique. For example
System.IO.IOException: Failed to bind to address
can match lots of test failures but the issue is specifically about this failure inWasm.Build.Tests
. Without the multi-line regex, how do I narrow down the match?
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: https://github.com/dotnet/arcade/issues/13253
If that isn't supported then what is the recommended way to identify failure messages that are not unique. For example
System.IO.IOException: Failed to bind to address
can match lots of test failures but the issue is specifically about this failure inWasm.Build.Tests
. Without the multi-line regex, how do I narrow down the match?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 ?
Reproduction Steps
browser-wasm linux Release WasmBuildTests
Known issue validation
Build: :mag_right: Result validation: :warning: 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. Validation performed at: 10/17/2023 1:46:13 AM UTC
Report
Summary