integration_test: move TestParseMultiline* family to transformation_test - #2412
Merged
rafaelwestphal merged 2 commits intoAug 31, 2026
Merged
Conversation
rafaelwestphal
force-pushed
the
westphalrafael/move-parse-multiline-to-transformation-tests
branch
4 times, most recently
from
August 31, 2026 15:59
36308f9 to
a90a7a5
Compare
franciscovalentecastro
requested changes
Aug 31, 2026
franciscovalentecastro
left a comment
franciscovalentecastro
left a comment
Contributor
There was a problem hiding this comment.
Requested changed : Update to regex the test names (e.g. ".*Multiline.*").
The TestParseMultilineFileJava, TestParseMultilineFileJavaPython, TestParseMultilineFileGolangJavaPython, and TestParseMultilineFileMissingParser integration tests are heavy GCE VM tests that only validate multi-line exception stack trace stitching for Go, Java, and Python. Moving them to transformation_test provides deterministic, millisecond-level multi-engine test coverage for language exception multiline parsing while reducing VM test execution time and eliminating unnecessary GCE resources in CI. Fixes b/553000750
rafaelwestphal
force-pushed
the
westphalrafael/move-parse-multiline-to-transformation-tests
branch
from
August 31, 2026 19:06
51efa26 to
6eb874f
Compare
…nsformation-tests
franciscovalentecastro
approved these changes
Aug 31, 2026
franciscovalentecastro
left a comment
franciscovalentecastro
left a comment
Contributor
There was a problem hiding this comment.
Ok! LGTM! I'm not seeing Build flakes failures from the transformation tests anymore.
rafaelwestphal
deleted the
westphalrafael/move-parse-multiline-to-transformation-tests
branch
August 31, 2026 20:57
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
The TestParseMultilineFileJava, TestParseMultilineFileJavaPython, TestParseMultilineFileGolangJavaPython, and TestParseMultilineFileMissingParser integration tests are heavy GCE VM tests that only validate multi-line exception stack trace stitching for Go, Java, and Python.
Moving them to transformation_test provides deterministic, millisecond-level multi-engine test coverage for language exception multiline parsing while reducing VM test execution time and eliminating unnecessary GCE resources in CI.
Related issue
Fixes b/553000750
How has this been tested?
Checklist: