Ankit Jain
Ankit Jain
After the fix in #8958 the reason for the failure is now - `System.Security.Authentication.AuthenticationException: The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot`.
This is failing regularly on PRs with ` Xunit.Runner.InProc.SystemConsole.TestingPlatform.XunitException: Class fixture type 'Aspire.Hosting.NodeJs.Tests.NodeAppFixture' threw in InitializeAsync` ``` at k8s.Watcher`1.CreateWatchEventEnumerator(Func`1 streamReaderCreator, Action`1 onError, CancellationToken cancellationToken)+MoveNext() at k8s.Watcher`1.CreateWatchEventEnumerator(Func`1 streamReaderCreator, Action`1 onError, CancellationToken...
`NodeAppFixture` writes its output to `diagnosticMessageSink`: https://github.com/dotnet/aspire/blob/44630f56ec00181ab87f97f01b045bf553df1514/tests/Aspire.Hosting.NodeJs.Tests/NodeAppFixture.cs#L30-L31 But I can't figure out how to get the output from that. Even using CWL doesn't show up anywhere. If I explicitly write...
I tried `/p:VSTestDiag=diag.log` also, but that doesn't have the messages logged via the `diagnosticMessageSink`.
> According to [xunit/xunit#2391](https://github.com/xunit/xunit/discussions/2391) this is not possible > > > `ITestOutputHelper` isn't compatible with any kind of fixture (class or collection). It's possible you're mis-using it in a way...
From [build](https://github.com/dotnet/aspire/actions/runs/15103027670): ``` node:events:502 throw er; // Unhandled 'error' event ^ Error: listen EADDRINUSE: address already in use :::49410 at Server.setupListenHandle [as _listen2] (node:net:1908:16) at listenInCluster (node:net:1965:12) at Server.listen (node:net:2067:7)...
https://github.com/dotnet/aspire/pull/7909/checks
In the last 53 runs 48 failed. Listing last 10 failures: | Run date | Outcome | | --------- | ------- | | Apr 8 4 AM | [Failed](https://github.com/dotnet/aspire/actions/runs/14324894524) |...
This test was un-quarantined, but the issue wasn't closed. Closing now. > I'm currently facing this issues in CI, is there any quick fix? Test are running locally but not...
Unquarantined by #9115 .