-
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
OSError: [WinError 122] The data area passed to a system call is too small
in Windows bdist CI job
#6544
Comments
I'm investigating this. Since this is not happening on PRs but is happening reliably on merges to One idea I'm considering is that maybe some filepath is slightly different. sarugaku/shellingham#8 suggests that maybe this error can show up when a too-long filepath is passed through to something using the Windows API to interact with the filesystem. |
I compared the logs between a recent successful PR build (build link) and The most significant difference I see is that on merges to From the logs there, it looks like those are setting up some kind of tracing. full logs (click me)
I wonder if maybe the mechanism there is somehow interfering with system tools in a way that I'm going to put up a PR trying to turn those jobs off. |
I think that #6563 fixed this. But I think we should leave it open until we see a few more successful CI runs on merges. I'm putting the |
@jameslamb Ah, thank you very much for finding this hidden rogue!
|
This issue has been automatically closed because it has been awaiting a response for too long. When you have time to to work with the maintainers to resolve this issue, please post a new comment and it will be re-opened. If the issue has been locked for editing by the time you return to it, please open a new issue and reference this one. Thank you for taking the time to improve LightGBM! |
Seems that Azure Pipelines builds are constantly failing for the
master
branch.For example, the latest one link: https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=16597&view=results
One of the failing jobs is Windows bdist
The text was updated successfully, but these errors were encountered: