Skip to content

[ci] Build GPU libraries on CPU nodes#10539

Merged
areusch merged 2 commits intoapache:mainfrom
driazati:cuda_cpu
Mar 12, 2022
Merged

[ci] Build GPU libraries on CPU nodes#10539
areusch merged 2 commits intoapache:mainfrom
driazati:cuda_cpu

Conversation

@driazati
Copy link
Member

@driazati driazati commented Mar 9, 2022

GPU capacity is more strained and expensive so we should stick to CPU when possible. This moves the GPU build to a CPU node (which is fine so long as the cuda libraries are present) and splits the C++ unit tests out to relevant areas (test steps where possible, otherwise it runs after the build).

cc @areusch

GPU capacity is more strained and expensive so we should stick to CPU when possible. This moves the GPU build to a CPU node (which is fine so long as the cuda libraries are present) and splits the C++ unit tests out to relevant areas (test steps where possible, otherwise it runs after the build)

commit-id:d385b28c
@driazati driazati marked this pull request as ready for review March 9, 2022 20:26
@github-actions github-actions bot removed the request for review from a team March 9, 2022 20:28
@github-actions github-actions bot requested a review from areusch March 10, 2022 00:25
commit-id:dcb084da
@areusch areusch merged commit 39487d8 into apache:main Mar 12, 2022
pfk-beta pushed a commit to pfk-beta/tvm that referenced this pull request Apr 11, 2022
* [ci] Build GPU libraries on CPU nodes

GPU capacity is more strained and expensive so we should stick to CPU when possible. This moves the GPU build to a CPU node (which is fine so long as the cuda libraries are present) and splits the C++ unit tests out to relevant areas (test steps where possible, otherwise it runs after the build)

commit-id:d385b28c

* Address comments

commit-id:dcb084da

Co-authored-by: driazati <driazati@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants