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

Roadmap: Fix flaky tests #3720

Closed
1 of 2 tasks
hcho3 opened this issue Sep 24, 2018 · 7 comments
Closed
1 of 2 tasks

Roadmap: Fix flaky tests #3720

hcho3 opened this issue Sep 24, 2018 · 7 comments

Comments

@hcho3
Copy link
Collaborator

hcho3 commented Sep 24, 2018

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

@khotilov
Copy link
Member

I could not reproduce the 1st one, but I will need to try with this specific version R-3.5.1patched later.

@hcho3
Copy link
Collaborator Author

hcho3 commented Sep 24, 2018

@khotilov I think the issue only appears for 32-bit R.

@hcho3
Copy link
Collaborator Author

hcho3 commented Sep 25, 2018

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.

@khotilov
Copy link
Member

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?

@hcho3
Copy link
Collaborator Author

hcho3 commented Sep 28, 2018

@khotilov I managed to re-produce the error as follows:

  1. Create a fresh Windows EC2 instance.
  2. Install R and Rtools.
  3. Compile XGBoost from source
  4. Install XGBoost into 32-bit R
  5. Run R tests inside 32-bit R

@trivialfis
Copy link
Member

@hcho3 Another weird test, on XGBoost Travis test:
https://travis-ci.org/dmlc/xgboost/jobs/448105204

On my Travis test:
https://travis-ci.com/trivialfis/xgboost/jobs/155019807

I also have some test failures on my machine but not on Travis, including shougun test and this one #3622.

@hcho3
Copy link
Collaborator Author

hcho3 commented Mar 13, 2019

Closing in favor of #4234

@hcho3 hcho3 closed this as completed Mar 13, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants