commit bb13a96931dd90d6570fa6151e19ef426d5c641f
author David Benjamin <davidben@google.com> Mon Dec 09 11:53:42 2024 -0500
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Mon Dec 09 17:30:25 2024 +0000
tree f725cf4b07a08bfbf5591ef51e5bab96dadded7d
parent 9559c4566a6d12194c42db5f3dbbcb5de35cfec2

Use BAZEL_CURRENT_REPOSITORY to pick up test data files

The old version of Bazel's runfiles.h header was incompatible with
bzlmod. Modules consuming BoringSSL could not successfully run tests.

There's now an extra parameter and a BAZEL_CURRENT_REPOSITORY macro
injected into the build, which resolves this. With this, running tests
from a downstream module now works:

    cd util/bazel-example
    bazelisk test @boringssl//:crypto_test

Change-Id: I43061cd4bc94cf69ed5b0d0f63715542f2a95d0e
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74067
Commit-Queue: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>

crypto/test/test_data.cc

diff --git a/crypto/test/test_data.cc b/crypto/test/test_data.cc
index f0e6922..fd77b5f 100644
--- a/crypto/test/test_data.cc
+++ b/crypto/test/test_data.cc
@@ -29,7 +29,8 @@
 std::string GetTestData(const char *path) {
 #if defined(BORINGSSL_USE_BAZEL_RUNFILES)
   std::string error;
-  std::unique_ptr<Runfiles> runfiles(Runfiles::CreateForTest(&error));
+  std::unique_ptr<Runfiles> runfiles(
+      Runfiles::CreateForTest(BAZEL_CURRENT_REPOSITORY, &error));
   if (runfiles == nullptr) {
     fprintf(stderr, "Could not initialize runfiles: %s\n", error.c_str());
     abort();