Add environment-agnostic scripts for running ctests and pytests #14992
Conversation
trxcllnt
added
3 - Ready for Review
|
@trxcllnt Just FYI, there are several PRs across RAPIDS adding |
There was a problem hiding this comment.
This is really helpful, I will definitely be using this feature when reproducing CI workflows (especially if I can get away with a "looser" reproduction for testing something specific). I am guessing this design is meant to make it easier to run tests in devcontainers?
|
@bdice yes this will help with running tests in devcontainers, but the primary motivation for this PR (and all the other similar ones I filed last night) is to provide a test script we can run in the DLFW/NVAIE builds. The test recipes change so frequently that it's difficult to keep the DLFW tests in sync for all repos. |
…nto fea/generic-test-scripts
…nto fea/generic-test-scripts
|
/merge |
Fixes error introduced in #14992 in `test_cpp_memcheck.sh` Extra line of parameters removed from the call to `run_cudf_memcheck_ctests.sh` Authors: - David Wendt (https://github.com/davidwendt) - https://github.com/jakirkham Approvers: - Bradley Dice (https://github.com/bdice) - Vyas Ramasubramani (https://github.com/vyasr) - Ray Douglass (https://github.com/raydouglass) URL: #15158
Description
This PR adds environment-agnostic
run_*_{ctests,pytests}.shscripts, and updatestest_*_{cpp,python}.shto call them.The
test_*_{cpp,python}.shscripts assume they're running in our CI environment, and they do more than just run the tests.This PR allows devs and downstream consumers to only run the tests, and skip the unrelated logic in
test_*_{cpp,python}.sh.Checklist