Uh oh!
There was an error while loading. Please reload this page.
test_runner: fix junit report on empty diagnostic - #65357
Conversation
nodejs-github-bot
commented
Aug 17, 2026
Review requested:
|
atlowChemi
left a comment
There was a problem hiding this comment.
Perhaps this should be tested with a .snapshot (see example
Signed-off-by: Lazizbek Ergashev <lazerg2@gmail.com>
f70a693 to
0a00f28Comparelazerg
commented
Aug 17, 2026
Switched to a snapshot in 0a00f28. |
nodejs-github-bot
commented
Aug 17, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #65357 +/- ##
==========================================
- Coverage 90.12% 90.11% -0.01%
==========================================
Files 752 752 Lines 251865 251872 +7 Branches 47353 47362 +9 ==========================================
- Hits 226991 226984 -7 + Misses 16223 16213 -10 - Partials 8651 8675 +24
🚀 New features to boost your workflow:
|
nodejs-github-bot
commented
Aug 19, 2026
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot
commented
Aug 19, 2026
Landed in 03fb384 |
context.diagnostic('')makes the junit reporter throw.treeToXMLguards the comment branch withif (comment), so an empty message falls through to the element branch andObjectEntries(attrs)gets called onundefined. The generator dies, the destination stream is destroyed, and the report is left without its closing</testsuites>.Comment nodes are already identified by
comment == nullelsewhere in the reporter, so the guard now checks the same way and an empty diagnostic renders as an empty XML comment.Fixes: #65355