fix: serialize e2e workflow runs and harden repo orchestration#186
Merged
arjuncooliitr merged 1 commit intomasterfrom Apr 17, 2026
Merged
fix: serialize e2e workflow runs and harden repo orchestration#186arjuncooliitr merged 1 commit intomasterfrom
arjuncooliitr merged 1 commit intomasterfrom
Conversation
Run the GitHub Actions Node matrix sequentially to avoid shared-credential rate limiting and Runtime namespace collisions across parallel e2e jobs. Also ensure runOne() always returns to the parent directory so one failing upstream repo does not cause subsequent repos to be cloned into nested paths.
chsrimanaswi
approved these changes
Apr 16, 2026
shazron
approved these changes
Apr 17, 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.
This PR addresses the remaining failures in the
app-test.ymlworkflow after disablingaio-lib-eventsandaio-lib-web.Root Cause
The workflow was running the Node matrix (
20.x,22.x,24.x) in parallel against the same Adobe credentials and the same Runtime namespace.That caused two classes of failures:
aio-lib-analyticsintermittently failed with429 Too Many Requestsaio-lib-runtimeintermittently failed because parallel jobs deployed and undeployed the same actions in the same namespaceThere was also a bug in the orchestrator: if one upstream repo failed inside
runOne(), the process never changed back to the parent directory, so later repos could be cloned inside the failed repo's directory tree.What This PR Changes
max-parallel: 1to the workflow matrix so Node versions run sequentiallyfail-fast: falseso all matrix jobs complete and report their individual statusprocess.chdir(name)inrunOne()with atry/finallyso the orchestrator always returns to the parent directory even when a repo's e2e test failsRelated Issue
https://jira.corp.adobe.com/browse/ACNA-4510
Motivation and Context
How Has This Been Tested?
npx jest --verboseTypes of changes
Checklist: