Build benchmarks in RMM CI

[harrism]

Fixes #940

Adds options to build tests and benchmarks to build.sh, and uses them in ci/gpu/build.sh

[jjacobelli]

Following what is done in other repos, you might need to update the conda build scripts to also build tests if Project Flash is enabled. See https://github.com/rapidsai/cudf/blob/branch-22.02/conda/recipes/libcudf/build.sh as example

[harrism]

@Ethyling that seems out of scope for this PR. This PR is about building benchmarks, not tests. Also I'm out sick and we are in burndown. so could you approve the present PR and just file an issue for this detail?

[jjacobelli]

@Ethyling that seems out of scope for this PR. This PR is about building benchmarks, not tests. Also I'm out sick and we are in burndown. so could you approve the present PR and just file an issue for this detail?

I think this is required to fix this CI issue: ci/gpu/build.sh: line 106: build/gtests/*: No such file or directory

Before this PR, the default value of BUILD_TESTS in CMake was ON, see: https://github.com/rapidsai/rmm/blob/branch-22.02/CMakeLists.txt#L38
Now it's OFF due to these changes:

• https://github.com/rapidsai/rmm/pull/941/files#diff-4d2a8eefdf2a9783512a35da4dc7676a66404b6f3826a8af9aad038722da6823R48
• https://github.com/rapidsai/rmm/pull/941/files#diff-4d2a8eefdf2a9783512a35da4dc7676a66404b6f3826a8af9aad038722da6823R99

This change only applies for non Project Flash builds: https://github.com/rapidsai/rmm/pull/941/files#diff-285f239638b8b5c5499ef5fda2e3db69adda7045e81556b4f2df478e99ab6263R71

But rmm is using Project Flash builds, so we also need to enable tests build for it.
As we are using the conda artifacts to run the tests in a Project Flash build, we need to add the test target when we are doing the conda build.

@harrism WDYT?

[harrism]

Ah, I see now. Unfortunately I'm out sick so will have to wait until next week unless you want to commit a fix.

[jjacobelli]

@harrism The tests and benchmarks are now building on PRs, but we only run the tests currently. Should we also run the benchmarks?

[harrism]

No, don't run the benchmarks. Benchmarking is a separate effort and would likely not be done on every PR. We just need to make sure PRs don't break the benchmark build.

[harrism]

Thanks for the help, @Ethyling !

[harrism]

Is this ready to merge now? Still needs ops approval.

[jjacobelli]

Is this ready to merge now? Still needs ops approval.

We are good to merge

[harrism]

@gpucibot merge