-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Quantized Grad Randomly Fails best_split_info.left_count
check
#5994
Comments
Linking this related issue: #5982 |
Even LightGBM's CI is sometimes randomly failing with this error. e.g., I just saw this on Windows: https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=14958&view=logs&j=67ae2ff8-4b33-578b-0813-9c0440091667&t=aed7750d-29a7-50d7-d7f0-fc7145577059
|
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. |
…5994) (microsoft#6092) * fix leaf splits update after split in quantized training * fix preparation ordered gradients for quantized training * remove force_row_wise in distributed test for quantized training * Update src/treelearner/leaf_splits.hpp --------- Co-authored-by: James Lamb <jaylamb20@gmail.com>
Description
When using the new 'use_quantized_grad' in python, lightgbm will randomly fail, giving this error:
Even when locking in the random state, it will fail randomly. Run the below code multiple times and you'll see it occasionally passes but fails maybe 1/2 the time?
Reproducible example
In google colab,
Environment info
Google Colab
Python 3.10.6
LightGBM version or commit hash: 4.0.0
Command(s) you used to install LightGBM
The text was updated successfully, but these errors were encountered: