Skip to content

Conversation

@andreachild
Copy link
Contributor

@andreachild andreachild commented Oct 30, 2025

Refactored flaky test TraversalExplanationTest.shouldApplyStrategiesCorrectly which has started failing more often when executed by github actions. This changeset changes the test to validate the individual parts of the TraversalExplanation triplets (strategy name, strategy category, steps) instead of using the prettyPrint output which can add line breaks in the middle of strategy and step names.

VOTE +1

@codecov-commenter
Copy link

codecov-commenter commented Oct 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (3.8-dev@054aa28). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff             @@
##             3.8-dev    #3259   +/-   ##
==========================================
  Coverage           ?   77.30%           
  Complexity         ?    15013           
==========================================
  Files              ?     1159           
  Lines              ?    71922           
  Branches           ?     8023           
==========================================
  Hits               ?    55599           
  Misses             ?    13273           
  Partials           ?     3050           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@xiazcy
Copy link
Contributor

xiazcy commented Oct 30, 2025

VOTE +1

…riplet parts instead of using the unreliable prettyPrint output which can add line breaks in the middle of strategy and step names.
@andreachild
Copy link
Contributor Author

Note that I had originally changed the test to add troubleshooting output but after the build failed for this PR I was able to determine the cause of the flakiness was the usage of prettyPrint output for validation. I changed the test to no longer rely on the prettyPrint output.

@andreachild andreachild changed the title Troubleshoot flaky TraversalExplanationTest Fix flaky TraversalExplanationTest Oct 31, 2025
@kenhuuu
Copy link
Contributor

kenhuuu commented Nov 3, 2025

VOTE+1 again after update to fix test

@Cole-Greer
Copy link
Contributor

VOTE +1

@andreachild andreachild merged commit 599e514 into apache:3.8-dev Nov 4, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants