Skip to content

[Twister2] Run local validation methods sequentially - #40864

Draft
bvolpato wants to merge 1 commit into
apache:masterfrom
bvolpato:bvolpato/serialize-twister2-validation
Draft

bvolpato wants to merge 1 commit into
apache:masterfrom
bvolpato:bvolpato/serialize-twister2-validation

Conversation

@bvolpato

Copy link
Copy Markdown
Contributor

Twister2's local test runner shares fixed worker ports and process-wide state between pipelines. Beam's parallel JUnit runner currently starts several validation methods at once, which can interfere during graph construction. This CI run failed in DAGMutableGraph.nodes() before reaching the job timeout.

Set beam.validatesRunner.parallelThreads=1 for the Twister2 batch validation task. This serializes its ValidatesRunner methods while retaining the existing test selection and general test-thread setting.

In an isolated container network, the default parallel run reproduced the same graph-iteration stack. The same selected pipeline and assertion cases passed with the new setting. Evaluated Gradle settings and live worker threads confirmed the change. The full scheduled suite and its timeout behavior remain unverified locally.

@github-actions github-actions Bot added runners twister2 size/xs XS: <10 lines changed labels Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

runners size/xs XS: <10 lines changed twister2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant