Skip to content

fix benchmark test hanging issue #4985

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

Merged

Conversation

frank-dong-ms-zz
Copy link
Contributor

benchmark test is hanging sometime on dotnet core 3.0 and 3.1 like below:
https://dev.azure.com/dnceng/public/_build/results?buildId=568308&view=logs&j=11c3dbcc-a5f4-5edd-335b-a8af5aa47d46&t=42ea9add-ee54-581f-d033-310ec15a7ff0
https://dev.azure.com/dnceng/public/_build/results?buildId=565081&view=logs&j=11c3dbcc-a5f4-5edd-335b-a8af5aa47d46&t=42ea9add-ee54-581f-d033-310ec15a7ff0
https://dev.azure.com/dnceng/public/_build/results?buildId=563397&view=logs&j=11c3dbcc-a5f4-5edd-335b-a8af5aa47d46&t=42ea9add-ee54-581f-d033-310ec15a7ff0

the reason of hanging is explained in comments like below:
// Don't use BaseTestClass's GetDataPath method instead for benchmark.
// BaseTestClass's static constructor is not guaranteed to be called before
// benchmark running (depending on CLR version this has different behaviour).
// The problem with executing BaseTestClass's static constructor when benchmark
// is running is it sometime cause process hanging when the constructor trying
// to load MKL, this is related to below issue:
// #1073

@frank-dong-ms-zz frank-dong-ms-zz requested a review from a team as a code owner March 31, 2020 04:16
@frank-dong-ms-zz frank-dong-ms-zz merged commit b148454 into dotnet:master Mar 31, 2020
@frank-dong-ms-zz frank-dong-ms-zz deleted the benchmark-hanging-fix branch April 7, 2020 04:29
@ghost ghost locked as resolved and limited conversation to collaborators Mar 18, 2022
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.

2 participants