cloud-fan commented on PR #55814:
URL: https://github.com/apache/spark/pull/55814#issuecomment-4430719032
### End-to-end validation result
Validated on the prior branch state with the `VALIDATION (DO NOT MERGE)`
plant commit (now dropped, force-pushed away — branch is now clean at
`db6d05943a9`). The plant carried 3 deliberately broken references; the
documentation generation job picked them up as follows.
**Summary block in the job log** (post-pipe, additive, drops no existing
lines):
```
========================================================================
Fatal javadoc errors (3):
========================================================================
1. /__w/spark/spark/core/target/java/org/apache/spark/Partition.java:6:
reference not found
* referencing the index field with the wrong separator: {@link
Partition.index} --
^
2.
/__w/spark/spark/sql/catalyst/src/main/java/org/apache/spark/sql/vectorized/ColumnarMap.java:26:
reference not found
* a class that does not exist: {@link
org.apache.spark.deliberately.NoSuchClass}
^
3.
/__w/spark/spark/sql/catalyst/src/main/java/org/apache/spark/sql/vectorized/ColumnarMap.java:27:
reference not found
* and a method that does not exist: {@link
ColumnVector#nonExistentMethod()}.
^
========================================================================
```
**GitHub Actions check panel annotations** (one per fatal diagnostic,
`title=javadoc`, multi-line message rendering the error + source snippet +
caret):
| File | Line | Message |
| --- | --- | --- |
| `sql/catalyst/.../ColumnarMap.java` | 26 | `reference not found` + `* a
class that does not exist: {@link org.apache.spark.deliberately.NoSuchClass}` +
`^` |
| `sql/catalyst/.../ColumnarMap.java` | 27 | `reference not found` + `* and
a method that does not exist: {@link ColumnVector#nonExistentMethod()}.` + `^` |
| `core/target/java/.../Partition.java` | 6 | `reference not found` + `*
referencing the index field with the wrong separator: {@link Partition.index}
--` + `^` |
This replaces the previous user experience where the PR check panel surfaced
only `Process completed with exit code 1` and the actionable diagnostics
required scrolling the raw job log.
**Self-check:** the captured count (3) matched javadoc's own `3 errors`
summary line, so no `::warning::` drift signal was emitted. If a future JDK
changes the Standard Doclet phase wording, the mismatch would surface that as a
workflow warning.
--
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]
