-
-
Notifications
You must be signed in to change notification settings - Fork 8.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
Roadmap: Fix flaky tests #3720
Comments
I could not reproduce the 1st one, but I will need to try with this specific version R-3.5.1patched later. |
@khotilov I think the issue only appears for 32-bit R. |
For tests/python/regression_test_utilities.py, we could solve it by migrating Python test to Jenkins (https://xgboost-ci.net), where we can use slave workers with more memory. |
I ran the test with some debug printouts many times locally and in a personal appveyor, but have never seen it fail :( I'm really curious to see the details for how it fails. How frequently would you estimate the failures were happening? |
@khotilov I managed to re-produce the error as follows:
|
@hcho3 Another weird test, on XGBoost Travis test: On my Travis test: I also have some test failures on my machine but not on Travis, including shougun test and this one #3622. |
Closing in favor of #4234 |
This issue is aimed at keeping track of flaky tests.
Rationale: some of existing tests tend to fail randomly, even when the pull request / branch update has nothing do to the tests. Since flaky tests bewilder community contributors and hamper developer productivity, they should be quickly addressed.
Note to maintainers: If you spot a flaky test, please report it here.
List of existing flaky tests
std::bad_alloc
exception due to memory shortageThe text was updated successfully, but these errors were encountered: