Conversation
|
🔗 Commit SHA: ea318c7 | Docs | View more details | Give us feedback! |
purple4reina
approved these changes
Sep 25, 2026
This branch has not been deployed
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.
What does this PR do?
public.ecr.aws/lambda/nodejs:22 and :24 were updated under their floating tags, and the new images changed runtime behavior the local Docker/RIE integration suite pins as goldens:
runtime_worker_pool_initializingdebug log record. ItsworkerCountfield reflects the container's visible CPU count, not anything the library controls, so it can't be pinned in a snapshot without becoming flaky across machines/runners with a different CPU allocation. Added it to the existing platform-noise filter inscripts/normalize_integration_logs.shinstead of baking the value in.integration_tests_local/run.shalready redacts requestId to XXXX, and the Node 26 golden (manual-throw-error_node26.json) already includes it. Node 24's golden had simply not been refreshed. Regenerated just that snapshot.Motivation
Discovered while investigating unrelated CI failures on #840
Testing Guidelines
Reproduced all four originally-failing combinations locally against the fresh base images (nodejs22.x/nodejs24.x, amd64/arm64) and confirmed they pass after this fix. Re-ran nodejs18.x/20.x/26.x to confirm no regressions.
Additional Notes
N/A
Types of Changes
Check all that apply