-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Fix Lambda CI log pollution issues #13546
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
Conversation
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 41m 26s ⏱️ Results for commit 397324c. |
gregfurman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
| except aws_client.lambda_.exceptions.ResourceNotFoundException: | ||
| pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
praise: Can't believe this is all it takes to declutter our logs 🫠
Motivation
Our CI logs are very noisy, including many avoidable WARNING and ERROR messages, making it difficult to debug real issues. In particular:
DeleteEventSourceMapping operation: The resource you requested does not exist.gets logged 27 timesChanges
test_create_event_filter_criteria_validationRelated
Discovered during AI Winter hackathon :)