-
Notifications
You must be signed in to change notification settings - Fork 5k
[QUIC] IsSupportedIsTrue failing on s390x #82154
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
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsIt is also failing on helix for linux-armv6: and linux-s390x: Originally posted by @am11 in #82108 (comment)
|
Once #82159 is merged, this should become disabled-test issue. |
This is another occurrence of #55979, i.e. msquic is silently dropping connections due to the machine being too slow. I've temporarily added statistics (6709e8e) and they show multiple dropped connections. I'm moving this to future as we don't have any solution for this problem. Maybe we could even close this against #55979 |
That is pretty sad that we cannot make single test reliable. I'm wondering if we can use the counter to adjust the expectation or decrease the concurrency for ARM. (or tune the drop threshold) cc: @nibanks |
You can't run a single test without failing? From my previous understanding, QUIC was getting overwhelmed by too much getting queued, and it was (by design) aborting the connection because it could no longer provide the time guarantees to have a reliable connection. But this wasn't caused by just 1 test. |
In this particular test, there is single listener and many parallel attempts to negotiate connection - this test was added recently to verify handling accept queue inside .NET. |
Failed for me on x64 as well while running tests on my VM over the weekend
|
For some reason I have mismatched the issues, the comments belong to #82769 🤦 |
Fixed by #115129 |
I'll re-open this and test it out in a PR, we have 3 different platforms disabled against it, so let's see. |
Hard to tell if it was fixed on s390x as the |
So ARMv6 is being removed? :( I'm using it in net8. |
Unfortunately the s390x Helix tests have been broken for a long time now, @directhex tried unsuccessfully to fix them but ran apparently into some network security issue where the outgoing connections from Microsoft/Azure systems to our builders are being blocked on the MS side. @giritrivedi and others on our side are currently working on setting up an alternative test environment that contacts our builders directly from GitHub, but that's not quite ready yet. I guess if there's no chance on the original builders getting fixed we might as well remove them. @leecow any thoughts? |
Yes, I think removing them makes sense at this point. |
We have deleted the CI validation. It has been broken for almost a year. The build images are outdated and tripping compliance checks. ARMv6 is community-maintained port. If you would like to submit patches to keep it up-to-date and working, we will be happy to accept them. |
My mistake. Thank you for catching it. I have closed wrong issue. (I meant to close #64674.) |
Uh oh!
There was an error while loading. Please reload this page.
SupportedLinuxPlatforms_IsSupportedIsTrue
It is also failing on helix for linux-armv6:
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-21c096763250462988/System.Net.Quic.Functional.Tests/3/console.f2cd77de.log?helixlogtype=result
and linux-s390x:
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-053a9df11f6d452495/System.Net.Quic.Functional.Tests/3/console.2de1fd1f.log?helixlogtype=result
Originally posted by @am11 in #82108 (comment)
EDIT:
I did a search in DevOps tests:
And seems like these 2 platforms:
Are the only remaining failing ones, as of now.
Known Issue Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: