Double check for events after parsing report data #2040
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the case that event files are found but cannot be read or parsed, we might write a session with no events. To mitigate this, we will double-check to make sure we've parsed the events properly before synthesizing a report file.
kmandrika
approved these changes
Oct 5, 2020
Coverage ReportAffected SDKsNo changes between base commit (6d8b572) and head commit (a2a8171b). Test Logs
NotesHTML coverage reports can be produced locally with Head commit (a2a8171b) is created by Prow via merging commits: 6d8b572 9aad55b. |
Binary Size ReportAffected SDKs
Test Logs
NotesHead commit (a2a8171b) is created by Prow via merging commits: 6d8b572 9aad55b. |
mrwillis21
deleted the
crashlytics-check-for-empty-events-after-parsing
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In the case that event files are found but cannot be read or
parsed, we might write a session with no events. To mitigate this,
we will double-check to make sure we've parsed the events properly
before synthesizing a report file.