-
Notifications
You must be signed in to change notification settings - Fork 1.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
Investigate and fix test failures #1131
Comments
Should we at least create list of failing tests? MultithreadedPrediction - MacOS - Debug FastTreeBinaryClassificationCategoricalSplitTest MacOS - Debug at Microsoft.ML.Runtime.RunTests.BaseTestBaseline.Done() in /Users/buildagent/agent/_work/1/s/test/Microsoft.ML.TestFramework/BaseTestBaseline.cs:line 149 TrainAndPredictIrisModelWithStringLabelTest MacOS - Debug |
@montebhoover , would you mind taking a look? |
These issues are fixed recently, some race condition issues. |
Our commit success rate is below 50% at this point.
We no longer have the annoying deadlock plaguing the builds, but somehow the builds are still failing quite often. Let's spend some time and improve that story.
From casual look, there is no single culprit: we seem to randomly fail to initialize build environment, and random tests seem to fail in random places. I guess this may have to do with resource-constrained runs: maybe we should actually try running xUnit tests sequentially and see if the sporadic failures go away?
The text was updated successfully, but these errors were encountered: