[release/8.0-staging] Remove an STJ deep nested object test causing occasional failures #120266
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
jeffhandley
approved these changes
Sep 30, 2025
|
The failure is a known infrastructure timeout issue unrelated to this PR. |
artl93
approved these changes
Oct 1, 2025
|
tell - test only change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Backport of #120247 to release/8.0-staging
/cc @jeffhandley
Customer Impact
We've seen some occurrences of this particular test causing stack overflows on test machines. The test was pushing the limits of previous test machine configurations, but it wasn't adding any material value beyond the other test scenarios. Removing this test case will eliminate unrelated test failures that have shown up while updating servicing CI pipelines.
Regression
The test repeatedly failed on old macOS version pipelines.
Testing
Successful build and test run in main.
Risk
Low. Removal of a test that wasn't adding material value.