Generate local resources in a .bazelrc file#90
Draft
Ahajha wants to merge 1 commit into
Draft
Conversation
A recent Bazel change now errors if a local resource is requested but it will never be available (bazelbuild/bazel@d9861632b5) This does another round of querying nvidia/rocm/amd-smi for GPU count and GPU memory so that we can fill these in. We use these internally to schedule tests on GPUs with memory counts, this makes a local GPU look a bit more like a remote one. This should allow smarter scheduling of local tests so the GPU isn't overloaded. Heavily Claude-generated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A recent Bazel change now errors if a local resource is requested but it will never be available (bazelbuild/bazel@d9861632b5)
This does another round of querying nvidia/rocm/amd-smi for GPU count and GPU memory so that we can fill these in. We use these internally to schedule tests on GPUs with memory counts, this makes a local GPU look a bit more like a remote one. This should allow smarter scheduling of local tests so the GPU isn't overloaded.
Heavily Claude-generated.