- Notifications
You must be signed in to change notification settings - Fork 129
Avoid trying to adjust dropped events on test results #384
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
Conversation
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.
It smells like a workaround, but in general all runners (test framework) require refactoring. If it doesn't harm other cases, I'm good with this change. Maybe just drop comment on this line, why is it necessary.
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors Expand to view the tests failures
|
| @jsoriano Do you plan to continue working on this PR or should it be closed? |
| Let's close it and continue droping the events on the pipeline. |
| Oh, I closed this thinking that it was #380 facepalm reopening, this is needed for elastic/integrations#1145. |
| Reopened again as #397 |
Pipelines can drop events, and they appear as null values in the test result, avoid trying to convert these null events into
common.MapStr, producing errors like: