anton-vinogradov opened a new pull request, #13302: URL: https://github.com/apache/ignite/pull/13302
## [IGNITE-28842](https://issues.apache.org/jira/browse/IGNITE-28842) ### Background The *Check java code* codestyle job intermittently looked broken with ~288 `cannot find symbol` errors for annotation-processor-generated classes (`*ViewWalker`, `*MessageSerializer`, `IDTOSerializerFactory`). Root cause: a single **real** compile error in a stale PR branch (a removed method still referenced after a clean text merge). javac drops all annotation-processor output when a compilation round has errors, so one real error cascades into hundreds of generated-class `cannot find symbol` errors that bury it. [IGNITE-28840](https://github.com/apache/ignite/pull/13299) and [IGNITE-28841](https://github.com/apache/ignite/pull/13300) chased this as a build-infra / parallelism problem; both were misdiagnoses. IGNITE-28841 in particular dropped the `-T 1C` parallel build added by [IGNITE-28823](https://github.com/apache/ignite/pull/13281). `-T 1C` was never the cause — the failure reproduces single-threaded. ### Change 1. Restore `-T 1C` on the codestyle / `test-compile` step (re-applies the IGNITE-28823 speed-up). 2. On compilation failure, make the job state it plainly and surface the real error: a GitHub `::error::` annotation ("compilation failed, not a checkstyle violation"), plus a collapsible group listing likely root-cause errors with the generated-class cascade (`*Walker`/`*Serializer`/`*Factory`, `internal.systemview`, `codegen.idto`) filtered out. Checkstyle-only failures are unaffected. ### Verification Filtering validated against a real failing build log (PR #13298 merge): from 288 errors it surfaces exactly the real one — `IgniteTxManager.java:[148,1] cannot find symbol: static deriveSyncMode`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
