ci: drop redundant glamsterdam serial exec leg from kurtosis-assertoor#21572
Merged
Conversation
glamsterdam.io passes --experimental.bal, and executor selection is `dbg.Exec3Parallel || cfg.experimentalBAL` (stage_execute.go), so the BAL flag forces parallel exec regardless of the ERIGON_EXEC3_PARALLEL=false the serial leg sets. The serial entry never exercised serial exec — it just duplicated the parallel run. Matches test-hive-eest.yml, whose glamsterdam-devnet shard is already parallel-only.
4d19ad9 to
5014d4a
Compare
yperbasis
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the
glamsterdamexec_mode: serialentry from thetest-kurtosis-assertoormatrix, leaving glamsterdam parallel-only.Why
glamsterdam.iopasses--experimental.bal, and executor selection isdbg.Exec3Parallel || cfg.experimentalBAL(execution/stagedsync/stage_execute.go). So the BAL flag forces parallel exec regardless of theERIGON_EXEC3_PARALLEL=falsethat the serial leg sets — the serial entry never actually ran serial, it just duplicated the parallel run (doubling runner-minutes for zero added signal). Serial exec also hard-fails on Amsterdam blocks by design (execution/stagedsync/exec3_serial.go).This matches
test-hive-eest.yml, whoseglamsterdam-devnetshard is already parallel-only.Validation
actionlintclean on the changed workflowregular(×2),pectra(×2),glamsterdam(parallel),caplin-minimal(×2)