Yicong-Huang opened a new pull request, #7053: URL: https://github.com/apache/texera/pull/7053
### What changes were proposed in this PR? `LoopIntegrationSpec` is the most expensive suite in the `amber-integration` CI job. Two changes, both spec-only (no engine change): | Change | Before | After | | --- | --- | --- | | Nested-loop input rows (iteration counts are data-driven via `i < len(table)`) | 3 rows → 3 outer x 3 inner | 2 rows → 2 outer x 2 inner | | Per-workflow completion deadline | 3 minutes | 90 seconds | Every loop iteration re-executes its region and respawns every worker in it (~2s per Python worker), so the two nested cases dominate the suite's cost; 2x2 halves their iterations while keeping the coverage that matters — nesting depth drives the `loop_counter`/`loop_start_id` envelope, and each loop level still takes its back-edge at least twice across the run. The single-loop cases keep the 3-row input so one loop takes the same back-edge twice consecutively. The deadline matters on macOS: the suite intermittently hangs mid-run there (observed in 3 of 4 attempts across two 2026-07-29 runs, e.g. [this failed job](https://github.com/apache/texera/actions/runs/30479437487/job/90673007976)), burning the whole deadline before `withRetry` re-runs the test. 90s is ~2.5x the slowest healthy case on the 3-core macOS runner, so a hang now costs ~1.5 min less per occurrence. Root-causing the hang itself is a separate follow-up. ### Any related issues, documentation, discussions? Closes #7052. Suite added in #5700. ### How was this PR tested? - Existing `LoopIntegrationSpec` assertions, updated for the 2x2 counts (outer 9→4, inner 3→2), pass in this PR's `amber-integration` CI job on both ubuntu and macOS. - `sbt WorkflowExecutionService/scalafmtCheckAll` passes locally. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 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]
