integ tests on private cdk lib fail since two days - ideas how to debug welcome about projen HOT 6 CLOSED

With no changes in your codebase? 🤯

To me the likeliest reasons seems that this command stops producing the correct output and fails silently:

cdk synth --app "ts-node -P tsconfig.dev.json test/EksAddons/EksAddonClusterAutoscaler.integ.ts" --no-notices --no-version-reporting --no-asset-metadata --no-path-metadata -o test/EksAddons/.tmp/EksAddonClusterAutoscaler.integ/assert.cdk.out > /dev/null

When you run this locally, can you make sure the .tmp folder is removed first?

from projen.

Yes - after digging some time in the ci container it seems cdk is not working at all - the command finishes with exit code 0 even if the integ.test.ts is deleted ... if I change it to cdk deploy, it's finished in no time with no output and exit code 0. of course no cdk.out is created

from projen.

Very odd! I would see that the app command does without the cdk cli. Sometimes that's giving a better error message. (That's the ts-node...)

from projen.

@markussiebert Did you ever get to the bottom of this?

from projen.

No was debugging in the gitlab executor pod - finally switched node image and it worked agin. Hadn't pinned the char, so maybe there was a change in the node image we used then...

from projen.

Okay. Closing as this seems to be an issue with Node or the AWS CDK.

from projen.