CI: Collect core dumps and broker executable on failure #509
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dmitrii Petukhov <[email protected]>
bbpetukhov
changed the title
Signed-off-by: Dmitrii Petukhov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable core dumps with unlimited size (by default the core dump size is zero thus no core dumps are created).
Implementation is based on the solution proposed in https://github.com/itamarst/gha-upload-cores?tab=readme-ov-file#getting-coredumps
Testing of the approach was done in the separate repository with simple app intentionally crashing (due to Segmentation Fault). It has been verified that core dump was created and uploaded as artifact.