Update the comments for StarlarkTransition#validate. It is no longer responsible for event handling since https://github.com/bazelbuild/bazel/commit/f129bb8dcefc2c9a9e8fcd87c98203f8627acf69.
PiperOrigin-RevId: 304063844
diff --git a/src/main/java/com/google/devtools/build/lib/analysis/skylark/StarlarkTransition.java b/src/main/java/com/google/devtools/build/lib/analysis/skylark/StarlarkTransition.java
index 1add6f1..1aa8c73 100644
--- a/src/main/java/com/google/devtools/build/lib/analysis/skylark/StarlarkTransition.java
+++ b/src/main/java/com/google/devtools/build/lib/analysis/skylark/StarlarkTransition.java
@@ -208,11 +208,7 @@
}
/**
- * Method to be called after Starlark-transitions are applied. Handles events and checks outputs.
- *
- * <p>Logs any events (e.g. {@code print()}s, errors} to output and throws an error if we had any
- * errors. Right now, Starlark transitions are the only kind that knows how to throw errors so we
- * know this will only report and throw if a Starlark transition caused a problem.
+ * Method to be called after Starlark-transitions are applied. Checks outputs.
*
* <p>We only do validation on Starlark-defined build settings. Native options (designated with
* {@code COMMAND_LINE_OPTION_PREFIX}) already have their output values checked in {@link
