-
Notifications
You must be signed in to change notification settings - Fork 8
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
Documentation on testing toolchain changes is out of date #43
Comments
I think the current process is something like the following. @comius does that look right, or is there a better way to do this?
|
I didn't see this issue. I will update docs. Yes, a lot has changed, for example toolchain definitions are not anymore in java_tools.
This is the best way to run all the tests. You could also unzip java_tools and add |
Does The approach in #43 (comment) still works for me. |
@comius ping? It would be nice to have a way to test java_tools changes without editing The following does not pick up any local modifications to
|
The mechanism should still work, except that you need to override both |
Is this the right idea? I can't get it to work:
I'm testing a repro for bazelbuild/bazel#14093, which causes JavaBuilder to unconditionally OOM, and the only way I can see the behaviour I'm introducing is by patching |
Facing the same issue. Unfortunately, your workaround @cushon doesn't seem to work anymore (we're on Bazel 5.2). Getting the following error. Does the workaround still work for you?
|
OK, there was 2 issues :
After that, I can verify the files located at /tmp/java_tools are copied over to /external/remote_java_tools/java_tools and are used. Seeing this error now (which can be temporary worked around by removing ErrorPronePlugin manually) :
|
For posterity, I think the complete steps for
And for
I think bzlmod changes mean it's necessary to override version (e.g. the |
Trying to do this again for bazelbuild/bazel#23246, the incantation for
To test a local build of turbine I also installed turbine to the local maven repo
and updated Bazel to refer to it: $ git diff MODULE.bazel
diff --git a/MODULE.bazel b/MODULE.bazel
index afabcbe5ff..73b938896c 100644
--- a/MODULE.bazel
+++ b/MODULE.bazel
@@ -113,7 +113,7 @@ maven.install(
"com.google.http-client:google-http-client:1.42.0",
"com.google.http-client:google-http-client-gson:1.42.0",
"com.google.j2objc:j2objc-annotations:1.3",
- "com.google.turbine:turbine:0.6.0",
+ "com.google.turbine:turbine:HEAD-SNAPSHOT",
"com.guardsquare:proguard-base:jar:7.5.0",
"com.ryanharter.auto.value:auto-value-gson-extension:1.3.1",
"com.ryanharter.auto.value:auto-value-gson-factory:1.3.1",
@@ -199,6 +199,7 @@ maven.install(
fail_if_repin_required = True,
lock_file = "//:maven_install.json",
repositories = [
+ "m2local",
"https://repo1.maven.org/maven2",
],
strict_visibility = True, Running Suggestions for a better way I could have accomplished that are welcome. |
@comius
This page is out of date: https://github.com/bazelbuild/java_tools/blob/master/docs/behind-the-release.md#manually-trying-out-java_tools-before-the-release-process
The
//src:java_tools_javaX.zip
target doesn't exist anymore (I think it's been replaced by e.g.//src:java_tools_zip
).It refers to
--java_toolchain
, which doesn't work with bazel at head due to the switch to toolchain resolution.The text was updated successfully, but these errors were encountered: