Skip to content
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

CICD: Capture core dump files from CI runs #640

Closed
spoonincode opened this issue Jan 16, 2023 · 0 comments · Fixed by #1850 or #1849
Closed

CICD: Capture core dump files from CI runs #640

spoonincode opened this issue Jan 16, 2023 · 0 comments · Fixed by #1850 or #1849
Assignees
Labels
CICD Anything dealing with the CI workflow behavior 👍 lgtm

Comments

@spoonincode
Copy link
Member

This is a carry over of eosnetworkfoundation/mandel#139, but I think we're pretty good now about capturing everything but core dump files? So I'm eliding the title to just reference core dumps.

Original issue:

b1's CI was diligent in archiving all logs, data files, and even core dump files from the tests it ran. This makes it easier to troubleshoot why a test failed compared to just seeing the stdout of ctest. Any refactor of Mandel's CI should strive to archive all these artifacts too.

@spoonincode spoonincode added the CICD Anything dealing with the CI workflow behavior label Jan 16, 2023
@bhazzard bhazzard changed the title Capture core dump files from CI runs CICD: Capture core dump files from CI runs Sep 28, 2023
@spoonincode spoonincode self-assigned this Oct 25, 2023
@spoonincode spoonincode moved this from Todo to In Progress in Team Backlog Oct 25, 2023
@spoonincode spoonincode moved this from In Progress to Awaiting Review in Team Backlog Nov 1, 2023
@github-project-automation github-project-automation bot moved this from Awaiting Review to Done in Team Backlog Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CICD Anything dealing with the CI workflow behavior 👍 lgtm
Projects
Status: Done
2 participants