Skip to content
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

tools: fix build breakages under //tools and add //tools build to CI #14615

Closed

Conversation

antoniovicente
Copy link
Contributor

Commit Message: tools: fix build breakages under //tools and add //tools build to CI
Additional Description:
Risk Level: n/a, tools change
Testing: n/a
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

Add //source/... //test/... and //tools/... to CI build targets

Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Antonio Vicente <avd@google.com>
ci/do_ci.sh Show resolved Hide resolved
@htuch htuch self-assigned this Jan 11, 2021
@antoniovicente
Copy link
Contributor Author

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Antonio Vicente <avd@google.com>
@foreseeable
Copy link
Contributor

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

@antoniovicente
Copy link
Contributor Author

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

ok, that's helpful. I see that the test is explicitly run in do_ci.sh with those extra flags. I think that making this test "manual" is the right work around for bazel test //tools/...

@antoniovicente
Copy link
Contributor Author

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

ok, that's helpful. I see that the test is explicitly run in do_ci.sh with those extra flags. I think that making this test "manual" is the right work around for bazel test //tools/...

I'm not sure what I'm missing, but the test fails for me when run as:
$ bazel test tools/envoy_headersplit:headersplit_test --spawn_strategy=local

…ls/...

Test can still be invoked manually as is done by do_ci.sh, see https://github.com/envoyproxy/envoy/blob/09134ffd78c89406f513e5bfe9a06397bd334184/ci/do_ci.sh#L269

Signed-off-by: Antonio Vicente <avd@google.com>
Signed-off-by: Antonio Vicente <avd@google.com>
@antoniovicente
Copy link
Contributor Author

antoniovicente commented Jan 11, 2021

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

ok, that's helpful. I see that the test is explicitly run in do_ci.sh with those extra flags. I think that making this test "manual" is the right work around for bazel test //tools/...

I'm not sure what I'm missing, but the test fails for me when run as:
$ bazel test tools/envoy_headersplit:headersplit_test --spawn_strategy=local

I think that the test calls in do_ci.sh for //tools/envoy_headersplit tests are missing the "test" verb. I would think that the resulting bazel calls to fail, not sure why it is not failing.

bazel_with_collection //tools/envoy_headersplit:headersplit_test --spawn_strategy=local

@foreseeable
Copy link
Contributor

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

ok, that's helpful. I see that the test is explicitly run in do_ci.sh with those extra flags. I think that making this test "manual" is the right work around for bazel test //tools/...

I'm not sure what I'm missing, but the test fails for me when run as:
$ bazel test tools/envoy_headersplit:headersplit_test --spawn_strategy=local

I think that the test calls in do_ci.sh for //tools/envoy_headersplit tests are missing the "test" verb. I would think that the resulting bazel calls to fail, not sure why it is not failing.

bazel_with_collection //tools/envoy_headersplit:headersplit_test --spawn_strategy=local

Thanks for pointing out this. It seems I made a mistake and i am going to fix it.

@antoniovicente
Copy link
Contributor Author

Posted https://github.com/envoyproxy/envoy/pull/12150/files#r554287142 about the //tools/envoy_headersplit:headersplit_test failure. I'm tempted to mark the test 'manual' and file an issue about it being broken since I have no idea how to fix it.

The headersplit_test need the libClang module to build, and libClang require the libclang.so from Clang.
But libclang.so is not contained in the Bazel sandbox environment, so I used --spawn_strategy=local to disable Bazel sandboxing for //tools/envoy_headersplit:headersplit_test as a workaround.

ok, that's helpful. I see that the test is explicitly run in do_ci.sh with those extra flags. I think that making this test "manual" is the right work around for bazel test //tools/...

I'm not sure what I'm missing, but the test fails for me when run as:
$ bazel test tools/envoy_headersplit:headersplit_test --spawn_strategy=local

I think that the test calls in do_ci.sh for //tools/envoy_headersplit tests are missing the "test" verb. I would think that the resulting bazel calls to fail, not sure why it is not failing.

bazel_with_collection //tools/envoy_headersplit:headersplit_test --spawn_strategy=local

Thanks for pointing out this. It seems I made a mistake and i am going to fix it.

I made the change as part of this PR, waiting for CI to tell me what happens.

@htuch
Copy link
Member

htuch commented Jan 13, 2021

The only test that fails is compile_time_options. Arguably this should not apply to //tools/.... This gets back to my earlier point about restricting this to a single build, which I think bazel.debug would make sense for. If you do that, you should be able to build cleanly.

Base automatically changed from master to main January 15, 2021 23:02
@htuch htuch added the waiting label Feb 7, 2021
@github-actions
Copy link

github-actions bot commented Mar 9, 2021

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Mar 9, 2021
@github-actions
Copy link

This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@github-actions github-actions bot closed this Mar 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale stalebot believes this issue/PR has not been touched recently waiting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants