The GitHub Actions job "Required Checks" on texera.git/xinyuan-loop-feb has failed. Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).
Head commit for run: 735bd7b791765b0007b58b27dbbf8377c90e3a18 / Xinyuan Lin <[email protected]> test(loop): read LoopEnd materialized results in the completion callback The materialized-result assertions added in e61681d695 failed deterministically in the amber-integration CI job (both LoopIntegrationSpec tests, on repeated attempts), while the workflow itself completed with the correct iteration counts and no FatalError. The read was the problem: it ran in the test body after client.shutdown() and threw a NoSuchElementException when an operator's external RESULT uri was absent. Restructure the read to match the working DataProcessingSpec pattern: - read each operator's materialized RESULT row count inside the ExecutionStateUpdate(COMPLETED) callback, while the engine and storage singletons are still alive; - tolerate operators whose external RESULT uri is absent (or whose iceberg document fails to open) by omitting them instead of throwing; - log the resolved per-operator materialized row counts, throughput counts, and any operators missing a RESULT uri, so a URI/count mismatch is visible in the CI output. Assertions are unchanged in intent (single LoopEnd = 3; nested outer = 9, inner = 3 after the per-outer-iteration reset) but now report expected-vs- actual. This is verified in the amber-integration CI job; the integration test cannot run locally on Windows (Python workers use signal.SIGKILL). Report URL: https://github.com/apache/texera/actions/runs/27458879617 With regards, GitHub Actions via GitBox
