-
Notifications
You must be signed in to change notification settings - Fork 27
Send Connect test instance logs to STDOUT for CI jobs to show the log in case of job failure #719
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
|
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
e1ce688 to
bab5a16
Compare
|
|
||
| [Python] | ||
| Enabled = true | ||
| Executable = /opt/python/9.9.9/bin/python |
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.
Intentionally triggering an error to confirm CI shows full Connect logs. To be removed.
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.
this is great. I was just going to ask for this! much easier to pick it out in the logs

The CI step "Get logs in case of failure" was not showing enough info while debugging CI failures.
Setting the logging output to STDOUT, instead of a file, should help to see all the info on GH action runs without the need to replicate locally.