(aws-lambda-nodejs): integration tests failing
See original GitHub issue❓ General Issue
The Question
Is anyone else experiencing issues with running integration tests on aws-lambda-nodejs module?
Btw… I’m running clean builds using docker and partial builds outlined in contribution guide… same results.
@aws-cdk/aws-lambda-nodejs: Bundling asset cdk-integ-lambda-nodejs-dependencies/external/Code/Stage...
@aws-cdk/aws-lambda-nodejs: /asset-input/node_modules/.bin/esbuild: /asset-input/node_modules/.bin/esbuild: cannot execute binary file
@aws-cdk/aws-lambda-nodejs: /Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/asset-staging.js:309
@aws-cdk/aws-lambda-nodejs: throw new Error(`Failed to bundle asset ${this.node.path}, bundle output is located at ${bundleErrorDir}: ${err}`);
@aws-cdk/aws-lambda-nodejs: ^
@aws-cdk/aws-lambda-nodejs: Error: Failed to bundle asset cdk-integ-lambda-nodejs-dependencies/external/Code/Stage, bundle output is located at /Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda-nodejs/test/cdk-integ.out/bundling-temp-20ef025878490e89e55410b3389cafecbc28e7782e3f1e15aab6c54679de3899-error: Error: docker exited with status 126
@aws-cdk/aws-lambda-nodejs: at AssetStaging.bundle (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/asset-staging.js:309:19)
@aws-cdk/aws-lambda-nodejs: at AssetStaging.stageByBundling (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/asset-staging.js:183:14)
@aws-cdk/aws-lambda-nodejs: at stageThisAsset (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/asset-staging.js:64:41)
@aws-cdk/aws-lambda-nodejs: at Cache.obtain (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/private/cache.js:28:17)
@aws-cdk/aws-lambda-nodejs: at new AssetStaging (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/core/lib/asset-staging.js:88:48)
@aws-cdk/aws-lambda-nodejs: at new Asset (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-s3-assets/lib/asset.js:25:25)
@aws-cdk/aws-lambda-nodejs: at AssetCode.bind (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda/lib/code.js:225:26)
@aws-cdk/aws-lambda-nodejs: at new Function (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda/lib/function.js:95:33)
@aws-cdk/aws-lambda-nodejs: at new NodejsFunction (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda-nodejs/lib/function.js:45:9)
@aws-cdk/aws-lambda-nodejs: at new TestStack (/Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda-nodejs/test/integ.dependencies.js:12:9)
@aws-cdk/aws-lambda-nodejs: Error: Command exited with status 1
@aws-cdk/aws-lambda-nodejs: at exec (/Users/rdjurasaj/code/robertd/aws-cdk/tools/cdk-integ-tools/lib/integ-helpers.js:336:15)
@aws-cdk/aws-lambda-nodejs: at IntegrationTest.cdkSynthFast (/Users/rdjurasaj/code/robertd/aws-cdk/tools/cdk-integ-tools/lib/integ-helpers.js:88:19)
@aws-cdk/aws-lambda-nodejs: at main (/Users/rdjurasaj/code/robertd/aws-cdk/tools/cdk-integ-tools/bin/cdk-integ-assert.js:19:33)
@aws-cdk/aws-lambda-nodejs: Error: cdk-integ-assert exited with error code 1
@aws-cdk/aws-lambda-nodejs: Tests failed. Total time (6m24.7s) | /Users/rdjurasaj/code/robertd/aws-cdk/node_modules/jest/bin/jest.js (6m7.6s) | cdk-integ-assert (17.1s)
@aws-cdk/aws-lambda-nodejs: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
@aws-cdk/aws-lambda-nodejs: npm ERR! code 1
@aws-cdk/aws-lambda-nodejs: npm ERR! path /Users/rdjurasaj/code/robertd/aws-cdk/packages/@aws-cdk/aws-lambda-nodejs
@aws-cdk/aws-lambda-nodejs: npm ERR! command failed
@aws-cdk/aws-lambda-nodejs: npm ERR! command sh -c cdk-test
@aws-cdk/aws-lambda-nodejs: npm ERR! A complete log of this run can be found in:
@aws-cdk/aws-lambda-nodejs: npm ERR! /Users/rdjurasaj/.npm/_logs/2020-12-10T22_29_55_269Z-debug.log
@aws-cdk/aws-lambda-nodejs: error Command failed with exit code 1.
@aws-cdk/aws-lambda-nodejs: Verifying integ.dependencies.js against integ.dependencies.expected.json ... info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build+test exited 1 in '@aws-cdk/aws-lambda-nodejs'
lerna WARN complete Waiting for 8 child processes to exit. CTRL-C to exit immediately.
real 29m5.385s
user 81m32.599s
sys 7m24.827s
❌ Last command failed. Scroll up to see errors in log (search for '!!!!!!!!')
Environment
- CDK CLI Version: 1.77.0
- Node.js Version: 15.4.0
- OS: macOS Mojave
Other information
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Unit Test and Integration Test for AWS Lambda/NodeJS in ...
Integration Test · Run the lambda in a local server · Add HTTP SDK to the project · Run the integration test.
Read more >Integration Test For AWS Lambdas — Easier than you might ...
The thing you "might" not know is that SAM runs your lambda function in a container itself, meaning that if you want to...
Read more >Testing Node serverless applications — AWS Lambda functions
Learn how to strike the right balance between unit, integration, and end-to-end testing for Node serverless applications.
Read more >Serverless Testing Strategies: Testing a Node.js + AWS ...
So we can just test it by calling it with a mock event and _context _(You can read up on these lambda handler...
Read more >Getting started with testing serverless applications
by Talia Nassi | on 20 SEP 2021 | in AWS Lambda, Events, ... Integration tests are important in serverless applications because they...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jogold That seems to work on targeted
aws-lambda-nodejs
build… Trying out the clean full docker build now.edit: full docker build worked too. Thanks @jogold 👍
It doesn’t fail on Linux because
esbuild
is symlinked even in the mounted volume.