-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[R-package] fix incorrect passing builds in valgrind checks (fixes #3704) #3705
Conversation
@@ -14,6 +14,7 @@ RDvalgrind \ | |||
|
|||
cat ${ALL_LOGS_FILE} | |||
|
|||
echo "writing valgrind output to ${VALGRIND_LOGS_FILE}" |
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.
/gha run r-valgrind
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.
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.
/gha run r-valgrind
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.
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.
ok I think the fix in this PR fixed it! Now this output at the end of the logs shows the correct numbers, so I can tell the stderr redirection is working
writing valgrind output to valgrind-logs.log
valgrind found 0 bytes definitely lost
valgrind found 0 bytes indirectly lost
valgrind found 336 bytes possibly lost
@@ -10,10 +10,11 @@ RDvalgrind \ | |||
--vanilla \ | |||
-d "valgrind --tool=memcheck --leak-check=full --track-origins=yes" \ | |||
-f testthat.R \ | |||
2>&1 > ${ALL_LOGS_FILE} || exit -1 | |||
> ${ALL_LOGS_FILE} 2>&1 || exit -1 |
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 was a silly mistake, sorry 😂
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. |
In https://github.com/microsoft/LightGBM/runs/1632971712?check_suite_focus=true, the valgrind checks on the R package failed but the CI job looked successful.
I think this was because of an incorrect use of shell output redirection in
.ci/test_r_package_valgrind.sh
.This PR tries to fix it (#3704).