You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue 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.
Based on the result of a recent run of the valgrind job (https://github.com/microsoft/LightGBM/runs/1349685476?check_suite_focus=true), it looks like recent commits have introduced an illegal read.
I'm marking this
blocking
for #3484 , because I think CRAN will reject the package if we don't fix this.Part of the issue here is that the check in https://github.com/microsoft/LightGBM/blob/cf69591b68c68a78ea4064e6941b8270b8a00eef/.ci/test_r_package_valgrind.sh for whether the valgrind test passed / failed is not strict enough. It currently only checks for the number of bytes lost, but should also be looking for "invalid read" and "invalid write" as well. I can fix that part.
The text was updated successfully, but these errors were encountered: