cloud-fan commented on PR #55548: URL: https://github.com/apache/spark/pull/55548#issuecomment-4318684757
The bait commit on this branch (`a4b30e83a3d` — `DO NOT MERGE: break a docstring`) successfully exercised the new diagnostic in CI on the latest run. Captured banner from the failing `Run / Documentation generation` job ([log](https://github.com/cloud-fan/spark/actions/runs/24922030737/job/72985418829)): ``` ============================================================================== Unidoc failed -- diagnostic summary ============================================================================== Javadoc crashed while generating: org/apache/spark/sql/connector/catalog/CatalogV2Implicits.IdentifierHelper.html Likely culprit: doc comment in org.apache.spark.sql.connector.catalog.CatalogV2Implicits.IdentifierHelper Javadoc can hard-exit (not just warn) on specific scaladoc patterns once they have been passed through genjavadoc -- wiki-style `[[Class]]` / `[[method]]` links or inline-backticked code refs in the Scala source for the class above are common triggers. Start by auditing any recent doc-string changes in that source file. NOTE: the '[error]' lines above on files under target/java/... are benign genjavadoc stubs -- every PR emits them and they do not cause the exit. Ignore them. ============================================================================== ``` The banner correctly named `CatalogV2Implicits.IdentifierHelper` — the exact class the bait commit broke — instead of leaving the reader to scroll past ~100 benign `[error]` lines on `target/java/...` stubs. Reverting the bait commit next. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
