[processor/logstransformprocessor] Re-enable flaky test and capture errors better #9776
Conversation
This file contains 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
dehaansa
changed the title
Added a changelog entry. |
djaglowski
approved these changes
May 9, 2022
djaglowski
pushed a commit
to djaglowski/opentelemetry-collector-contrib
that referenced
this pull request
May 10, 2022
…rrors better (open-telemetry#9776) * Re-enable flaky test and capture errors better for logstransformprocessor * Add additional log to processor simple test * Cleanup & lint * trigger new test run * Add sort in while awaiting change to otel-log-collection * Update changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description: Resolving flaky test. This PR is here to try to replicate in github actions & validate errors
Link to tracking Issue: #9761
Underlying issue appears to be unsorted operators. Created a PR to address underlying issue open-telemetry/opentelemetry-log-collection#480 but until that is available, I added the Sort directly in the processor, which should address the unreliable test.