The GitHub Actions job "Required Checks" on texera.git/test-network-output-buffer-spec has failed. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 5c9917a3df7711f1e232885cd8ef1dd2bcae6447 / Xinyuan Lin <[email protected]> test(amber): add unit test coverage for NetworkOutputBuffer Pin the per-receiver batched-tuple sender used by every concrete Partitioner subclass: - Construction: batchSize defaults to ApplicationConfig.defaultDataTransferBatchSize; `to` and `dataOutputPort` are exposed as immutable accessors; an empty buffer at construction does not implicitly auto-flush. - addTuple: does not flush below batchSize; auto-flushes exactly at the batchSize boundary; produces one DataFrame per batch with tuples in insertion order, with no leak across batches; routes DataFrames to the configured receiver on the data (non-control) channel. - flush: sends a DataFrame with the buffered tuples and resets the buffer when non-empty; is a no-op when called on an empty buffer (so a regression that sends an empty DataFrame breaks here); assigns monotonically increasing sequence numbers across multiple flushes; the same sequence-number stream is shared with the StateFrame on the same channel (pin so a regression that side-channels StateFrame breaks). - sendState: pre-flush bookend drains pending tuples in their own DataFrame BEFORE the StateFrame; pre-flush is a no-op when nothing is pending; trailing post-state flush leaves the buffer clean for the next addTuple. - Edge cases: batchSize=1 flushes after every addTuple; batchSize=0 collapses to the same behavior because the `>=` guard fires for any non-empty buffer (characterized so a future tightening to `>` breaks on purpose). The test wires a real NetworkOutputGateway with a recording handler, so the assertions exercise the production codepath end-to-end (sequence-number assignment, channel-id construction, payload type) rather than mocking the gateway. Closes #4957 Report URL: https://github.com/apache/texera/actions/runs/25408185469 With regards, GitHub Actions via GitBox
