WiP: evaluate Bazel native coverage in CI.#5953
WiP: evaluate Bazel native coverage in CI.#5953htuch wants to merge 2 commits intoenvoyproxy:masterfrom
Conversation
|
This pull request has been automatically marked as stale because it has not had activity in the last 7 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! |
stale
bot
added
the
stale
|
This pull request has been automatically closed because it has not had activity in the last 14 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! |
stale
bot
removed
the
stale
For now, try and figure out if bazel native coverage will fly from a performance perspective. DO NOT SUBMIT Signed-off-by: Harvey Tuch <htuch@google.com>
|
This pull request has been automatically marked as stale because it has not had activity in the last 7 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! |
stale
bot
added
the
stale
|
This pull request has been automatically closed because it has not had activity in the last 14 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! |
2 participants
For now, try and figure out if bazel native coverage will fly from a performance perspective.
DO NOT SUBMIT
Signed-off-by: Harvey Tuch htuch@google.com