-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aws-lambda-nodejs] failing frequently on PR builds #11222
Comments
I've noticed the same as well. @eladb - can you take a look? |
What is the error message in this case? And is this also the cause for failed builds on master? |
Pasting the log snip directly here since logs are retained for only 30 days.
|
@jogold - I see the same error message on master albeit intermittently, every 10th or so build. Could this be related to the new docker limits on image pulls? I believe the new limits are 100/6hours for unauthenticated users and 200/6hours for 'Free' users. |
Coverage requirement is being dropped temporarily to reduce the chance of this error - #11370 |
Could totally be because that's a thing that changed, but how does that manifest itself as a "coverage" drop??? |
FYI this will most likely be fixed with #11289 since it seems related to the Parcel implementation ( I was not able to reproduce either but I think there's some kind of race condition when tests for multiple modules run in parallel. The coverage drop comes from the failing |
Replace Parcel with esbuild for bundling. esbuild offers [impressive performances](https://esbuild.github.io/) compared to Parcel. Moreover everything can be configured via the CLI. This means that we don't need to play with the user `package.json` file anymore. Add full Windows support for local bundling. Refactor and clean-up. Closes #10286 Closes #9130 Closes #9312 Resolves #11222 BREAKING CHANGE: local bundling now requires `esbuild` to be installed. * **lambda-nodejs**: `projectRoot` has been replaced by `depsLockFilePath`. It should point to your dependency lock file (`package-lock.json` or `yarn.lock`) * **lambda-nodejs**: `parcelEnvironment` has been renamed to `bundlingEnvironment` * **lambda-nodejs**: `sourceMaps` has been renamed to `sourceMap`
|
Looks like the build is now (randomly?) failing in the tests for |
Maybe linked to an issue when running parallel jest tests |
See build log
|
@nija-at Not sure if you're sure of the cause, but the test for
@aws-cdk/aws-lambda-nodejs
frequently fails. Seen it couple times now, even though the code is unrelated. Always seems to resolve itself after merging master branch in againOriginally posted by @iRoachie in #11092 (comment)
The text was updated successfully, but these errors were encountered: