[test optimization] Fix error suppression bug when jest fails with test suite errors#7524
Conversation
Overall package sizeSelf size: 4.6 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.6 | 81.92 kB | 813.08 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7524 +/- ##
=======================================
Coverage 80.23% 80.23%
=======================================
Files 731 731
Lines 31194 31194
=======================================
Hits 25027 25027
Misses 6167 6167 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
BenchmarksBenchmark execution time: 2026-02-13 11:01:30 Comparing candidate commit 6df7651 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 229 metrics, 31 unstable metrics. |
…st suite errors (#7524)
…st suite errors (#7524)
What does this PR do?
If a
jesttest session failed with:we would flip the exit code to 0, even though there is an error that we should not suppress, the test suite one. Since we were only checking test errors, not test suite errors, this was missed.
Motivation
Fix wrongly suppressed errors.