cloud-fan commented on PR #55563: URL: https://github.com/apache/spark/pull/55563#issuecomment-4332466658
End-to-end validation on this branch (since reverted): pushed a deliberate 182-char comment in `core/src/main/scala/org/apache/spark/Aggregator.scala` to trip scalastyle's `LineLengthChecker` (commit `4e1f1fee726`), then reverted (`365edf9a4c1`). Two claims confirmed on that CI run: 1. **Decoupling**: only the **Linters** job failed. Build modules (api/catalyst/hive-thriftserver, core, hive, sql, sparkr, all pyspark variants, streaming/connect, yarn), Java 17 + Java 25 Maven builds, Documentation generation, Docker integration tests, K8s integration test, and TPC-DS all stayed green despite a violation in `core` — so the cascade through `(Compile / compile)` is gone. 2. **Annotation emitter**: the lint-job failure surfaced as an inline `Scalastyle: File line length exceeds 100 characters` annotation pointing at `core/src/main/scala/org/apache/spark/Aggregator.scala:31` on the Files-changed tab, exactly as advertised. (One unrelated flake on `Build modules: mllib-local, …` — failed at the runner's `Free up disk space` cleanup step before any compile, not the PR.) -- 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]
