commit 0c617b39f1f5fe04233439399c177519a7c4353c
author Richard Levasseur <rlevasseur@google.com> Wed Sep 13 11:37:17 2023 -0700
committer Copybara-Service <copybara-worker@google.com> Wed Sep 13 11:38:37 2023 -0700
tree d862a090f8670011272ee91286fa468ee0c7bbba
parent 7c1b139fc0a26b69131b62a019dac3ce9d31082d

Load Python rules in integration tests instead of using builtins (#2)

This is to facilitate moving the rule implementation out of Bazel itself and into rules_python. This also makes the tests pass when an allowlist is used to enforce that the Python rules are being loaded through rules_python instead of used from builtins.

This the same change as before, but with some internal fixes applied.

PiperOrigin-RevId: 565113515
Change-Id: I999dbfaace8cce2168e718093fe418d548ab1b73

src/test/shell/integration/modify_execution_info_test.sh

diff --git a/src/test/shell/integration/modify_execution_info_test.sh b/src/test/shell/integration/modify_execution_info_test.sh
index 9e98dc7..d627c99 100755
--- a/src/test/shell/integration/modify_execution_info_test.sh
+++ b/src/test/shell/integration/modify_execution_info_test.sh
@@ -170,6 +170,8 @@
   mkdir -p "$pkg" || fail "mkdir -p $pkg"
   echo "load('//$pkg:shell.bzl', 'starlark_shell')" > "$pkg/BUILD"
   cat >> "$pkg/BUILD" <<'EOF'
+load("@rules_python//python:py_binary.bzl", "py_binary")
+
 starlark_shell(
   name = "shelly",
   output = "ok.txt",