Fix DLRMv3 fbgemm_gpu loading with hardcoded Bazel paths #2439
+16
−28
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.
Problem
The DLRMv3 harness was using hardcoded Bazel build paths specific to Meta's internal build system:
torch.ops.load_library("//deeplearning/fbgemm/fbgemm_gpu:sparse_ops")
torch.ops.load_library("//deeplearning/fbgemm/fbgemm_gpu:sparse_ops_cpu")
This caused failures when running outside that environment:
FAILED to load sparse_ops_cpu in position: Could not load this library: /deeplearning/fbgemm/fbgemm_gpu:sparse_ops
FAILED to load sparse_ops_cpu in jagged: Could not load this library: /deeplearning/fbgemm/fbgemm_gpu:sparse_ops
FAILED to load sparse_ops_cpu in jagged tensors: Could not load this library: /deeplearning/fbgemm/fbgemm_gpu:sparse_ops
FAILED to load sparse_ops_cpu in hstu attention: Could not load this library: /deeplearning/fbgemm/fbgemm_gpu:sparse_ops
Fixes #2429