(contributing): Build failures don't always include !!!!!!!!
#28515
Labels
@aws-cdk/aws-route53resolver
bug
This issue is a bug.
effort/medium
Medium work item – several days of effort
p3
Describe the bug
When a PR CodeBuild build fails, the end of the build text says:
Unfortunately, not all failures have that string. That being present seems to be specific to JSII failures?
Expected Behavior
The error should be on a line that has
!!!!!!!!
or be pretty obvious/recent in the build output. The message saying how to find a failure should help lead a user to the failure.Current Behavior
Due to the parallel nature of the build, the error was way earlier without a
!!!!!!!!
and mixed in with other "random" output:Reproduction Steps
!!!!!!!!
.Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
N/A
Framework Version
No response
Node.js Version
N/A
OS
N/A
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: