Include field error
true for spans representing failure results
#168
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
We noticed for Github Actions or even CircleCI buildevents that the step or command that represents the failure does not include the boolean field error set to
true
We use this value to signal the error state in the UI:
AND in the calculation to display error rates on the Home page for Buildevents:
Short description of the changes
Includes the field error true along with sending status failed and failure reason for a span