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
Running the valgrind checks on the R package in #3703, I see the following.
==2176== LEAK SUMMARY:
==2176== definitely lost: 318 bytes in 10 blocks
==2176== indirectly lost: 576 bytes in 9 blocks
==2176== possibly lost: 336 bytes in 1 blocks
==2176== still reachable: 312,088,759 bytes in 55,705 blocks
==2176== of which reachable via heuristic:
==2176== newarray : 4,264 bytes in 1 blocks
==2176== suppressed: 0 bytes in 0 blocks
==2176== Reachable blocks (those to which a pointer was found) are not shown.
==2176== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==2176==
==2176== For lists of detected and suppressed errors, rerun with: -s
==2176== ERROR SUMMARY: 153 errors from 14 contexts (suppressed: 0 from 0)
This means that either that PR or some new changes on master have introduced issues that will prevent the next release of LightGBM from making it to CRAN. I'll test if this is related to #3699 or if it's already an issue on master and update this issue.
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.
Running the valgrind checks on the R package in #3703, I see the following.
This means that either that PR or some new changes on
master
have introduced issues that will prevent the next release of LightGBM from making it to CRAN. I'll test if this is related to #3699 or if it's already an issue onmaster
and update this issue.full log from #3703
As a separate issue, it's problematic that despite new "definitely lost" and "indirectly loss" counts, the build https://github.com/microsoft/LightGBM/runs/1632971712?check_suite_focus=true passed. That points to a bug in the CI script which needs to be fixed.
The text was updated successfully, but these errors were encountered: