You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "eugenegujing (via GitHub)" <gi...@apache.org> on 2026/08/04 22:25:52 UTC

[I] add unit test coverage for CoordinatorTimerService [texera]

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

   ### Task Summary
   
   `amber/src/main/scala/org/apache/texera/amber/engine/architecture/coordinator/CoordinatorTimerService.scala` owns the two recurring timers that drive statistics collection: one for frontend status updates and one for runtime-statistics persistence. 
   
   The class has no spec, and the coordinator specs that construct a `CoordinatorProcessor` all pass `CoordinatorConfig(None, None, None, None)`, which means only the interval-empty path is ever taken and no timer is ever scheduled in a unit test. The end-to-end tests happen to use `CoordinatorConfig.default`, so the timers do run there, but nothing asserts the scheduling decision, the message payload, the idempotence guard, the cancel-and-clear behavior, or the independence of the two handles.
   
   ### Task Type
   
   - [ ] Refactor / Cleanup
   - [ ] DevOps / Deployment / CI
   - [x] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other


-- 
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: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] add unit test coverage for CoordinatorTimerService [texera]

Posted by "aglinxinyuan (via GitHub)" <gi...@apache.org>.
aglinxinyuan closed issue #7311: add unit test coverage for CoordinatorTimerService
URL: https://github.com/apache/texera/issues/7311


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org