-
Notifications
You must be signed in to change notification settings - Fork 10.4k
EnableAzurePipelinesReporter for helix #8094
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
Conversation
Test Run Aborted... *shakes fist* |
I don't see any results :( |
Yep, me neither. Investigating. |
adding @MattGal in case there's anything else we might need to enable other than just the flag |
I wonder if some of our custom logic might be the cause. |
The good news is that it doesn't blow up with the issue I saw when I tried it the first time: #7368 |
We also don't have xunit reporter turned on, not sure if that is a requirement for the azdo helix stuff |
@alexperovich any idea why only random small subset of test results got uploaded to VSTS? |
XUnit results are not published to MC either |
Nice so it looks like azdo flags missing test results as an error, so maybe we don't need the explicit test discovery check I just added to our scripts anymore if it fails the run with
|
It doesn't have reported tests because of your check that prevented the reporter from running. |
Tests are not reported because RTX and xUnit XML are not the same. |
Blocked dotnet/arcade#2161 |
This should be unblocked now (dotnet/arcade#2286), but @pakrym has switched teams. @JunTaoLuo can you take a look at completing this? |
2f00d10
to
5102e55
Compare
Even more than the usual number of warnings in the Helix build output. And, it looks like the Helix run caught some flaky tests. Either fix some of the warnings and update this branch or retry AspNetCore-helix-test before we merge. |
Hrm helix run looks pretty normal with only interop and one IIS test failing, but the test results all seem to have failed with missing result files, or am I looking at the wrong view? |
I think the warnings are due to dotnet/arcade#1605. I'm not sure there's a fix for it. I'll retry the tests though. |
Could it be the additional flaky helix test run that's messing things up when it produces a second trx file? Maybe we can we try removing that additional pass from the runtest.cmd/sh and see if that affects the count? |
Hmm this seems suspicious in the log:
Maybe the uploading of the results went awry. |
Ugh, thats just a bug with the trx parsing. Trx is sooo complicated for a simple type of data. I'll fix it. |
Cool, that's good news, well hopefully its just that bug on the parsing, and all our test data is already there |
PR with fix: dotnet/arcade#2648 |
@alexperovich can you let me know which version of the sdk will have this fix when a build of it is available? |
The build is currently waiting behind another build. I will let you know when a version containing the fix is available. |
Version 2.0.0-beta.19230.6 has been published with the fix. |
28dfffc
to
8c2a5bb
Compare
Still missing some test results as Helix is only reporting from one of the .trx files. Will wait for another SDK update. |
974d43a
to
ad66401
Compare
Woot! I think all the test results are being reported now, thanks @alexperovich for the many fixes. I think after a final round of tests, this will be ready to get checked in! |
@@ -23,6 +23,7 @@ namespace Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.Http2 | |||
{ | |||
[OSSkipCondition(OperatingSystems.MacOSX, SkipReason = "Missing SslStream ALPN support: https://github.com/dotnet/corefx/issues/30492")] | |||
[MinimumOSVersion(OperatingSystems.Windows, WindowsVersions.Win10)] | |||
[SkipOnHelix(Queues = "Debian.8.Amd64.Open")] // Debian 8 uses OpenSSL 1.0.1 which does not support HTTP/2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note to self: double check the versino of OpenSSL on Debian 8 agents and see if there's a way to manually update the version to one that supports HTTP/2
Fix: #7368
Fix: #8087