Skip to content

Conversation

@marcosnav
Copy link
Contributor

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.

@github-actions
Copy link

github-actions bot commented Oct 30, 2025

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-10-30 22:49 UTC

@github-actions
Copy link

github-actions bot commented Oct 30, 2025

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
5257 4001 76% 0% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: ce961da by action🐍


[Python]
Enabled = true
Executable = /opt/python/9.9.9/bin/python
Copy link
Contributor Author

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.

Copy link
Contributor

@joshyam-k joshyam-k Oct 30, 2025

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

@marcosnav
Copy link
Contributor Author

Tried forcing an error to confirm logs pass through. YES! we get full output now :)

Screenshot 2025-10-30 at 2 09 10 p m

@joshyam-k joshyam-k merged commit f2e79e6 into main Oct 30, 2025
16 checks passed
@joshyam-k joshyam-k deleted the mnv-ci-log-output branch October 30, 2025 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants