Ankit Jain

It was showing it as unmatched, which prompted me to change the pattern. This is what I see right now:

> This was working before - seems like the issue table insertion and PR linking is not though. Yeah, I'm seeing the same issue in https://github.com/dotnet/runtime/issues/93023 . It should have...

This happened in the latest run, and only in one helix job which ran on PERFTIGER173 (which is not the one we have been seeing problems). Also, almost all the...

> I can't reproduce this locally, i.e. the dotnet.framework.wasm file built locally from the files in the `obj/` dir appears valid. Could this be https://github.com/dotnet/runtime/issues/88148 ?

@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...

> 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...

> > 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...

Are the xunit bits here just for testing? They should be with the rest of the runner stuff that we have in xharness.

> @radical do you remember why this change was needed https://github.com/dotnet/runtime/commit/eceb5c8951ca3e5902a6eecdd594f82916ff4762 ? We didn't want native relinking for the linker tests. You can remove that `WasmBuildNative=false` from the command line,...