-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel CI failure: Bazel test command is too long on Windows #3742
Comments
@damienmg , the tests are returned by bazel query command, can we just run the tests instead of doing a query first? |
That would create other issues but we could if we replace all the place we
use queries to select tests (I have tried to do so for some of them, query
are complex to write).
…On Fri, Sep 15, 2017, 3:27 PM Yun Peng ***@***.***> wrote:
@damienmg <https://github.com/damienmg> , the tests are returned by bazel
query command, can we just run the test instead of do a query first?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3742 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADjHf4vCaQ-d9Bq1sX29xQy8h3YP1e7Bks5sintFgaJpZM4PY9xJ>
.
|
Why not just to use the standard approach on windows and provide respone file as input instead of too long command line? This is what LibreOffice build tool chain is doing in all places. See for example: [1]. |
This is what all our intermediate tool support, we could certainly add that
support to Bazel.
…On Mon, Sep 18, 2017, 9:09 AM David Ostrovsky ***@***.***> wrote:
Why not just to use the satndard approach on windows and providde respone
file as input instead of too long command line? This is what LibreOffice
build tool chain is doing in all places.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa367156(v=vs.85).aspx
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3742 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADjHf8-CQdItqF_U0FQVzb3o-KDrX2ttks5sjhcNgaJpZM4PY9xJ>
.
|
FYI, @laszlocsomor . This is why Windows is still red while all tests passes. |
Thanks @meteorcloudy ! I also see this in the log:
Notice it says "java/om/google/..." instead of "java/com/google/..." |
Yes, I noticed the same thing, I guess it's somehow caused by the command line being too long? |
I think we can work around this problem if we create |
New occurrence: http://ci.bazel.io/view/Dashboard/job/bazel-tests/1036/consoleFull
|
Am I understanding this correctly that Windows is removing characters from the middle of the command line when the length is too long? testdata --> testdaa, com --> om, by --> y |
I don't know what mangled the pattern names in the error message... But I have a fix for the long command problem: https://bazel-review.googlesource.com/c/bazel/+/16910 |
Add recursive test_suite rules for all tests that ci.bazel.io runs for Windows, and set the top-level test_suite as the CI test target. Doing so shortens the command line and works around #3742 I verified that the old set of tests are the same as the new set. Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa PiperOrigin-RevId: 169242858
related commit: bazelbuild/continuous-integration@61b5986 |
This one is fixed, once and for all :) |
Fixes #3742 Change-Id: Ibfa1909e387e9734040b00523cc9388a386e0bf4 PiperOrigin-RevId: 169538023
http://ci.bazel.io/blue/rest/organizations/jenkins/pipelines/CR/pipelines/bazel-tests/runs/383/nodes/36/steps/468/log/?start=0
All tests passed, but we are getting an error:
I suspect this is because the bazel test command exceeds the max length (8K) of command line on Windows.
The text was updated successfully, but these errors were encountered: