Fix handling of duplicate error messages in test cluster logs #69494
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.
As part of #68333 I mistakenly broke the support for de-duplication of error messages. We use a normalized form of the error as a
Map
key to handle de-duplication for us. I naively replaced this with the original message so that we don't lose the original message timestamp. This obviously completely breaks de-duplication as we are adding the unique messages w/ timestamp as the map key. The other side effect of this is that for very large logs with lots of repeated errors, we end up loading them all into memory and blowing out the build JVM heap 😨This change reverts to using the normalized message as the Map key while retaining the original message as well. The net result is reverting back to us dumping log messages formatted like so: