Kunal Pathak

We can target for 15 minutes and see how many we can accomodate. We can adjust it depending on the coverage we get in those 15 minutes.

I tried it on my machine, and I still see it for 40 minutes. Do you see any benchmarks in this list that should have not run? ``` Intel Core...

I see it to be 12 minutes. ``` Global total time: 00:12:01 (721.7 sec), executed benchmarks: 39 ```

not sure what is the problem. I am able to run this fine.

``` System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_Cancellation_Test_Http3.PostAsync_CancelDuringRequestContentSend_TaskCanceledQuickly(chunkedTransfer: False, mode: Token) [FAIL] Expected cancellation exception, got: System.Net.Http.HttpRequestException: Connection handshake was canceled due to the configured timeout of 00:00:10 seconds elapsing. (127.0.0.1:63734) ---> System.Net.Quic.QuicException: Connection handshake was...

I believe the root cause is same as for https://github.com/dotnet/runtime/issues/91757 and https://github.com/dotnet/runtime/issues/101463, but the exception thrown is different, so opening a separate issue.

@ljharb , it **does** fail for `node-v8`. So it is a bug in evalmd and not in `node-chakracore`. ```cmd E:\git\qs>node -pe process.versions { http_parser: '2.7.0', node: '7.5.0', v8: '5.4.500.48', uv:...

This seems to be still failing in https://github.com/dotnet/runtime/pull/101859 which included the fix made in #101800

/azp run runtime-coreclr superpmi-replay, runtime-coreclr superpmi-diffs

> > do you have any suggestions to fix[ this build error](https://dev.azure.com/dnceng-public/public/_build/results?buildId=698281&view=logs&j=5d780cf0-7dc0-5aa0-741e-ecc17ef09a05&t=a5e632ba-8fa1-50be-a73e-ed850090cc2e&l=2620) - unknown opcode: rdvl, for Windows on Arm64 ? > > I do not think we need to...