-
Notifications
You must be signed in to change notification settings - Fork 310
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
[FEA] Reduce the testing done by CI #1555
Comments
cuDF and RMM have updated to version 1.12, we have been requested to update as well. This PR is dependent on: * rapidsai/raft#211 * rapidsai/cuhornet#49 Also disabled some unit tests to reduce our CI time, since we've started seeing timeouts. Issue #1555 will fully address this issue. Authors: - Chuck Hastings (https://github.com/ChuckHastings) Approvers: - Brad Rees (https://github.com/BradReesWork) URL: #1553
This issue has been labeled |
This issue has been labeled |
Modified the most expensive C++ tests to run fewer tests. Closes #1555 Added an option (like in the rmat tests) to run a specific test file if the developer wants to manually run larger tests. For example: ```tests/COARSEN_GRAPH_TEST --gtest_filter=file_ben* --test_file_name=test/datasets/ljournal-2008.mtx``` The smaller graphs *should* be small enough to test things. Once we add C++ code coverage we should be able to verify this. On my local workstation this reduced the time spent executing the C++ tests by about 25 minutes. Authors: - Chuck Hastings (https://github.com/ChuckHastings) Approvers: - Kumar Aatish (https://github.com/kaatish) - Seunghwa Kang (https://github.com/seunghwak) URL: #1989
The amount of testing we currently do in CI is causing timeout issues. We need to reevaluate what we are testing as part of CI to reduce the total time.
As an example, I ran
make test
on my linux box and saw the following two results appear:It seems like 20 minutes spent running these two C++ unit tests is really too high. The point of the unit tests is to verify the functionality of the code, not to measure performance (that should be a different suite of tests).
The text was updated successfully, but these errors were encountered: