Repository navigation
Conversation
|
Review requested:
|
@ocodista Is there anything specific you would like help with? π |
I'm still not sure where the call is being made so I can wrap it with a try-catch. Also, it takes an eternity to build node on my PC, is there a way to make it faster? π This way would be easier to add console logs and find it π |
Reporter detailsWe create the reporter here: https://github.com/nodejs/node/blob/4b3d964a8c01c4b541fc85d3a419b58524806f04/lib/internal/test_runner/utils.js#L165-L172 Basically we call compose on the node/lib/internal/test_runner/test.js Line 192 in 4b3d964 This node/lib/internal/streams/compose.js Line 24 in 4b3d964
This depends on what OS you are using, but I suggest having a look at Line 220 in 4b3d964
If you are only changing JS modules (and no src c++ code etc) you can avoid additional builds by setting the Lines 548 to 558 in 4b3d964 |
This goal of this PR is to solve the issue 48937
Where the test silently fails if there's an exception inside the Custom test Reporter.
I created this repo with a minimum reproduction of the bug.
I also created a new test (that's currently failing) to check if the Custom Reporter error message will be shown.
I'm still working on getting the exception from the custom reporter (start step) and displaying it on the test result.
Any help/guidance would be appreciated!