Skip to content

Improve error logging context during screenshot or ast failure#415

Merged
chadlwilson merged 3 commits intomasterfrom
improve-error-logging
Jul 30, 2025
Merged

Improve error logging context during screenshot or ast failure#415
chadlwilson merged 3 commits intomasterfrom
improve-error-logging

Conversation

@chadlwilson
Copy link
Contributor

No description provided.

These are impossible to trace to gauge-ruby as they have no context, and the backtrace is swallowed. Log more detail, and allow using debug to get to backtrace of the error.

Signed-off-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com>
Signed-off-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com>
Signed-off-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com>
@gaugebot
Copy link

gaugebot bot commented Jul 30, 2025

@chadlwilson Thank you for contributing to gauge-ruby. Your pull request has been labeled as a release candidate 🎉🎉.

Merging this PR will trigger a release.

Please bump up the version as part of this PR.

Instructions to bump the version can found at CONTRIBUTING.md

If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.

@chadlwilson
Copy link
Contributor Author

Actually, these messages are passed as json so probably don't need to do it line-by-line.

This one cost me all sorts of GoCD debugging madness today after triggering some selenium-webdriver bug with ruby timeouts during http calls. Sigh. 😅

@chadlwilson chadlwilson merged commit 86b9fc4 into master Jul 30, 2025
56 of 57 checks passed
@chadlwilson chadlwilson deleted the improve-error-logging branch July 30, 2025 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants