Yicong-Huang opened a new issue, #4501: URL: https://github.com/apache/texera/issues/4501
### Task Summary `CheckpointSpec` (`amber/src/test/scala/org/apache/texera/amber/engine/faulttolerance/CheckpointSpec.scala`) takes ~70s in CI to run only **two** active assertions, making it the single slowest spec in the Scala test step (about 26% of test execution time on a recent run). The two active tests just verify that a default `ControllerProcessor` and `DataProcessor` are serializable; the rest of the file is commented out. Despite that, the spec spins up **two** Pekko `ActorSystem`s: - One in `beforeAll` (`CheckpointSpec.scala:62`), named `"CheckpointSpec"` — never referenced by the active tests - One created lazily by `AmberRuntime.serde` (`AmberRuntime.scala:39-48`), named `"Amber"` — used by `chkpt.save(...)` for `SerializationExtension` There is no roundtrip across the two systems (no `chkpt.load(...)` is called), so the second `ActorSystem` boot looks redundant. Eliminating the duplicate boot, plus removing unused class-level setup (`buildWorkflow(...)` at line 48, which is only referenced by commented-out tests), should significantly cut spec runtime. ### Priority P2 – Medium ### Task Type - [x] Refactor / Cleanup - [x] Testing / QA -- 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]
