-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Re-enable more networking tests for innerloop #18406
Comments
* Test cleanup for System.Net.Security #3144 - Removed TODO because Begin/End were added back in #8358 and the issue is closed #7825 - Original issue from April 2016. Cannot repro today. Re-enabling to watch for future failures. #11170 - Can't repro failures on multiple OSs. Re-enabling to watch for future failures. #11345 - Outerloop tests are passing and stable for thousands of iterations. Tentatively moving to innerloop to watch for potential future failures. #12107 - removed TODO because issue is closed #9130, #10909, #11624, #14177, #14505 - duplicate issues failing because of an intermittent error (remote party closed transport stream) not exclusive to the test which occurs in Outerloop runs for other NetSecurity tests. Re-enabling them and leaving them in innerloop to get more data. #8744, #12683, #12706, #12728 - duplicate issues failing because of an intermittent error (credentials package not recognized) not exclusive to the test which occurs in Outerloop runs for other NetSecurity tests. Re-enabling them and leaving them in innerloop to get more data. * Remove unused netsecurity tests helper * Remove unused test helper
Tracking networking test reliability with #19687. |
|
Pls leave Outerloop as-is. In general, networking tests which access a remote endpoint or even loopback still need to be outerloop for now. |
This issue probably shouldn't be marked 2.0 though. @karelz Why is this issue 2.0? At this point, we are not ready yet to move all networking tests to inner loop. |
Oh. Never mind. I see that this issue is closed. So, no action required. Thx. |
BTW: I set milestones on issues which are closed, so that it is easy to find out when they were fixed / resolved as won't fix, etc. |
PR dotnet/corefx#11341 moved the majority of networking tests to outerloop due to infrastructure issues. This issue will track putting back tests as we strengthen the test infrastructure to allow more networking tests to run as innerloop.
The text was updated successfully, but these errors were encountered: