Drop racy parallel pre-build step from inapp-e2e-tests workflow#1055
Open
franco-zalamena-iterable wants to merge 3 commits into
Open
Drop racy parallel pre-build step from inapp-e2e-tests workflow#1055franco-zalamena-iterable wants to merge 3 commits into
franco-zalamena-iterable wants to merge 3 commits into
Conversation
After the SDK-170 migration of this workflow to ubuntu-latest + KVM (#1048, commit 7d4a80b), every PR opened against master has been failing the In-App Message E2E Tests check at the build stage: Execution failed for task ':integration-tests:mergeDebugAndroidTestResources'. > Cannot access output property 'blameLogOutputFolder' … > Failed to create MD5 hash for file '.../merged_res_blame_folder/.../values-az.json' as it does not exist. with this warning a few lines earlier: Detected multiple Kotlin daemon sessions at kotlin/sessions The 'Pre-download Gradle and Build (Parallel with Emulator)' step backgrounded a separate Gradle invocation that was meant to assemble the APKs while the emulator booted. On macos-15-intel the background process was resource-starved during emulator boot (2 cores / slow HVF) so it usually finished or stalled before the action's Gradle started. On ubuntu-latest + KVM both Gradle processes get real CPU and run in true parallel, racing on the same integration-tests/build/intermediates directory. Affected runs: - feature/sdk-338-mobile-inbox-customization: 5 failures - fix/SDK-412-UUA-Naming-inconsistencies: 1 failure - SDK-170-emulator-network-trace: green (warm cache made the race window negligible — masked the regression during review) Removing the parallel pre-build is sufficient. The action's script already invokes ':integration-tests:connectedDebugAndroidTest' which transitively builds the APKs it needs. Expected wall-clock impact: +30-90s on a cold Gradle cache, traded for 'all PRs can run this check'. Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
sumeruchat
approved these changes
Jun 1, 2026
Contributor
sumeruchat
left a comment
sumeruchat
left a comment
There was a problem hiding this comment.
Approving :)
Great job on the comment explaining why the pre-build only started racing after the ubuntu-latest + KVM migration. That's exactly the context that keeps someone from re-adding it later.
Confirmed the action's own connectedDebugAndroidTest builds both APKs transitively, so the removed step was redundant.
joaodordio
approved these changes
Jun 1, 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
3 participants
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.
✏️ Description
The merge for fixing ci tests missed a part regarding the setup, the pr had cache and this was not picked up for e2e messages tests