-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
make Select_LargeNumber_Succcess exclusive #105751
Conversation
Tagging subscribers to this area: @dotnet/ncl |
|
||
[Collection(nameof(DisableParallelization))] |
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.
If this is exhausting process-wise file descriptor limit, instead of disabling parallelization on this test, should we run this inside RemoteExecutor
?
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.
I'm not sure if the limits are per process or per user. We may try both if this fails or we can disable it explicitly on tvOS
and Catalyst
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
contributes to #105688.
While this test handles fd exhaustion via try/catch it can impact other tests.