Skip to content
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

Remove ThreadPool event tests #56680

Merged
merged 1 commit into from
Aug 6, 2021
Merged

Conversation

noahfalk
Copy link
Member

@noahfalk noahfalk commented Aug 1, 2021

The threadpool events being verified by this test aren't
guaranteed to occur given the test code. All of them are
the results of background timers and relative execution
speed of work items. Given the relatively low event coverage
of the existing test and my historical understanding that
specific events don't often regress, trying to stabilize this test
is probably more hassle than it is worth.

This is part of resolving #48727

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@noahfalk noahfalk self-assigned this Aug 1, 2021
@noahfalk
Copy link
Member Author

noahfalk commented Aug 1, 2021

/azp run runtime-coreclr jitstress

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@noahfalk
Copy link
Member Author

noahfalk commented Aug 2, 2021

/azp run runtime-coreclr jitstress

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@noahfalk noahfalk marked this pull request as ready for review August 2, 2021 03:52
@noahfalk
Copy link
Member Author

noahfalk commented Aug 2, 2021

/azp run runtime-coreclr jitstress

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@noahfalk noahfalk marked this pull request as draft August 2, 2021 09:58
The threadpool events being verified by this test aren't
guaranteed to occur given the test code. All of them are
the results of background timers and relative execution
speed of work items. Given the relatively low event coverage
of the existing test and my historical understanding that
specific events don't often regress, trying to stabilize this test
is probably more hassle than it is worth.
@noahfalk noahfalk changed the title Reenable ThreadPool event tests Remove ThreadPool event tests Aug 4, 2021
@noahfalk noahfalk marked this pull request as ready for review August 5, 2021 00:30
@noahfalk noahfalk requested a review from josalem August 5, 2021 00:30
@noahfalk noahfalk merged commit 3675d99 into dotnet:main Aug 6, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants