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

[ci] Make valgrind check stricter #3536

Merged
merged 1 commit into from
Nov 7, 2020

Conversation

jameslamb
Copy link
Collaborator

An issue caught by valgrind was recently introduced onto master because the valgrind CI job didn't catch it: #3525 .

This PR fixes that so similar problems are caught in the future. Specifically, it will now fail builds where valgrind produces "invalid read" (like #3525) or "invalid write" (like https://www.stats.ox.ac.uk/pub/bdr/memtests/valgrind/lightgbm/tests/testthat.Rout) errors.

if [[ ${invalid_writes} -gt 0 ]]; then
echo "valgrind found invalid writes: ${invalid_writes}"
exit -1
fi
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/gha run r-valgrind

@StrikerRUS StrikerRUS merged commit c0ffb71 into microsoft:master Nov 7, 2020
@jameslamb jameslamb deleted the ci/valgrind branch February 7, 2021 03:36
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants