57004738b1
Since the 0.21 upgrade, the host `$PATH` is not forwarded anymore by default to the sandboxes in charge to realize Bazel actions. This default change broke the `py_binary` rule among other things. Every python binary is wrapped in a stub in charge to setup the execution environment. Currently, this stub's shebang points to a `/usr/bin/env python` which cannot be resolved with the current `$PATH`. This results in breaking any build pipeline requiring the use of python at some point. On top of the incorrect shebang, the stub template is unable to find the actual python binary using `SearchPath`. This PR fixes those two things by re-writing the stub template shebang to the actual python binary and by substituting the faulty default python binary lookup to the right one.
56 lines
1.1 KiB
Nix
56 lines
1.1 KiB
Nix
{ stdenv, lib, writeText, runCommandCC, bazel }:
|
|
|
|
let
|
|
WORKSPACE = writeText "WORKSPACE" ''
|
|
workspace(name = "our_workspace")
|
|
'';
|
|
|
|
pythonLib = writeText "lib.py" ''
|
|
def foo():
|
|
return 43
|
|
'';
|
|
|
|
pythonBin = writeText "bin.py" ''
|
|
from lib import foo
|
|
|
|
assert foo() == 43
|
|
'';
|
|
|
|
pythonBUILD = writeText "BUILD" ''
|
|
py_library(
|
|
name = "lib",
|
|
srcs = [ "lib.py" ],
|
|
)
|
|
|
|
py_test(
|
|
name = "bin",
|
|
srcs = [ "bin.py" ],
|
|
deps = [ ":lib" ],
|
|
)
|
|
'';
|
|
|
|
runLocal = name: script: runCommandCC name { preferLocalBuild = true; } script;
|
|
|
|
workspaceDir = runLocal "our_workspace" ''
|
|
mkdir $out
|
|
cp ${WORKSPACE} $out/WORKSPACE
|
|
mkdir $out/python
|
|
cp ${pythonLib} $out/python/lib.py
|
|
cp ${pythonBin} $out/python/bin.py
|
|
cp ${pythonBUILD} $out/python/BUILD.bazel
|
|
'';
|
|
|
|
testBazel = runLocal "bazel-test-builtin-rules" ''
|
|
export HOME=$(mktemp -d)
|
|
cp -r ${workspaceDir}/* .
|
|
${bazel}/bin/bazel --output_base=/tmp/bazel-tests/wd\
|
|
test \
|
|
--test_output=errors \
|
|
--host_javabase='@local_jdk//:jdk' \
|
|
//...
|
|
|
|
touch $out
|
|
'';
|
|
|
|
in testBazel
|