-
Notifications
You must be signed in to change notification settings - Fork 4.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
Disable fuzz coverage test on Bazel CI #16940
Conversation
Hi @meteorcloudy, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
@antoniovicente assign you because you seem to have some background based on the referenced issue. |
@meteorcloudy it might be worth discussing the path forward with @antoniovicente first, but if we're going to proceed with this PR, we'll need DCO signoff (see https://github.com/envoyproxy/envoy/blob/main/CONTRIBUTING.md#dco-sign-your-work) |
envoyproxy#16542 has been keep Envoy red on Bazel CI for a long time, it doesn't make sense to keep a failing test if it's not going to be fixed. Signed-off-by: Yun Peng <pcloudy@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine to disable this in order to get the bazel CI back to a green state.
That sounds good, as an aside I think the problem may be related to some libc++ flag configuration? |
envoyproxy#16542 has been keep Envoy red on Bazel CI for a long time, it doesn't make sense to keep a failing test if it's not going to be fixed. Signed-off-by: Yun Peng <pcloudy@google.com>
#16542 has been keep Envoy red on Bazel CI for a long time, it doesn't make sense to keep a failing test if it's not going to be fixed.