Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bazel CI] Error in resolve_tools: Pass an executable or tools argument to ctx.actions.run or ctx.actions.run_shell instead of calling ctx.resolve_tools. #23631

Open
sgowroji opened this issue Sep 16, 2024 · 2 comments
Labels
team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug untriaged

Comments

@sgowroji
Copy link
Member

sgowroji commented Sep 16, 2024

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4128#0191f902-c676-4637-9e7d-471b450c2ddb

Platform: Windows, Macos, Ubuntu

Logs:

(04:15:41) ERROR: C:/b/bk-windows-xd7b/bazel-org-repo-root/bazel/src/java_tools/buildjar/java/com/google/devtools/build/java/turbine/BUILD:29:13: in _native_image rule //src/java_tools/buildjar/java/com/google/devtools/build/java/turbine:turbine_direct_graal:
Traceback (most recent call last):
	File "C:/b/wvcmlhs6/external/rules_graalvm+/internal/native_image/rules.bzl", line 61, column 40, in _graal_binary_implementation
		graal_inputs, _ = ctx.resolve_tools(tools = [
Error in resolve_tools: Pass an executable or tools argument to ctx.actions.run or ctx.actions.run_shell instead of calling ctx.resolve_tools.
Use --noincompatible_disallow_ctx_resolve_tools to temporarily disable this check.
(04:15:41) ERROR: C:/b/bk-windows-xd7b/bazel-org-repo-root/bazel/src/java_tools/buildjar/java/com/google/devtools/build/java/turbine/BUILD:29:13: Analysis of target '//src/java_tools/buildjar/java/com/google/devtools/build/java/turbine:turbine_direct_graal' failed
(04:15:41) ERROR: Analysis of target '//src/test/shell/bazel:bazel_java17_test' failed; build aborted: Analysis failed
(04:15:41) INFO: Elapsed time: 33.518s, Critical Path: 30.22s
(04:15:41) INFO: 3428 processes: 5709 action cache hit, 253 remote cache hit, 2158 internal, 860 local, 157 worker.
(04:15:41) ERROR: Build did NOT complete successfully

Culprit:

Steps:

git clone https://github.com/bazelbuild/bazel
git reset 7b8d07253adf84d5e3d46ac915a1440e518fab3c  --hard
export USE_BAZEL_VERSION=7b8d07253adf84d5e3d46ac915a1440e518fab3c
bazel build //src:bazel.exe //src:bazel_jdk_minimal //src:test_repos //src/main/java/... 

CC Greenteam @comius

@sgowroji sgowroji added type: bug untriaged team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts labels Sep 16, 2024
@tjgq
Copy link
Contributor

tjgq commented Sep 16, 2024

Note: probably not Windows-specific. Taking a look.

@tjgq
Copy link
Contributor

tjgq commented Sep 16, 2024

Sent sgammon/rules_graalvm#459 to fix upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: bug untriaged
Projects
None yet
Development

No branches or pull requests

2 participants