You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
To validate that ENVOY_BUG conditions have code coverage, is it possible to issue warnings or a make a required check that a condition is tested for success and failure by leveraging the existing coverage report?
Motivation:
Encourages failure condition testing, especially since these are fatal in debug mode
Ensures that Envoy can continue safely even if hitting an ENVOY_BUG condition in release mode.
Difficulties:
With a normal coverage report, it's opaque whether the ENVOY_BUG condition passes or fails.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Description
To validate that
ENVOY_BUG
conditions have code coverage, is it possible to issue warnings or a make a required check that a condition is tested for success and failure by leveraging the existing coverage report?Motivation:
Difficulties:
See
#14575
The text was updated successfully, but these errors were encountered: