aglinxinyuan opened a new issue, #8037:
URL: https://github.com/apache/texera/issues/8037

   ### Task Summary
   
   `ComputingUnitMaster` sits at 67 of 93 fully-covered lines. 
`ComputingUnitMasterSpec` is already a strong suite at 34 tests, but two things 
in the file are unreached:
   
   - **`createAmberRuntime`'s body** (lines 75–80) — the method that builds the 
`AmberClient` over the process-wide actor system, wiring the workflow context, 
physical plan and coordinator config. No test enters it.
   - **The two cleanup `catch` blocks** in `dropCollections` and 
`deleteReplayLog` warn rather than propagate, and the scala-logging guard on 
each leaves one arm untaken.
   
   Most of the rest of the file is genuinely not unit-testable and should not 
be chased: `main()` would `System.exit` the shared test JVM, and the cleanup 
branch sits behind a private static final boolean.
   
   ### Task Type
   
   - [x] Testing / QA
   
   ### Was this issue authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 5)
   


-- 
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]

Reply via email to