jest exists before report is generated about jest-html-reporter

[zeevrosental]

if it helps, i noticed that no report is generated if jest is running with --forceExit.

it seems that it closes before the report is created.

[Hargne]

I will have a look at it ASAP!

[RobertGary1]

Is it an option to use the synchronous I/O calls in nodeJs? Not sure what version of NodeJs introduced them.

[Hargne]

I'm pretty sure it's been possible for a long time to do synchronous calls with fs (correct me if I'm wrong). I'm unsure if that's the solution in this case though. It is a little weird as I haven't heard this from anyone else using the plugin.
What version of Node are you using, by the way?

[RobertGary1]

I'm using node.js v8.9.1

[Hargne]

I have been trying to reproduce this issue, but without any luck. I'm wondering if there might be something related to the structure of the project that you are working on that causes this issue, since there haven't been any reported issues where the reports haven't been generated up until now.

Theoretically, the asynchronous method createReport should not be aborted just because Jest has initialized prior to it finishing. This is due to the fact that Jest expects the testResultsProcessor (this module) to instantaneously return back the test result (which is done at the end of index.js).

Would you mind attempting to debug what may cause this issue to occur and post any findings here?

Thanks!

[Hargne]

Closing this for now. Re-open if you still think it is a relevant issue.

[zeevrosental]

i think this is still a problem. other reporters are not creating this problem(junit reporter).

[Hargne]

Is is possible to provide more details of the environment you ran the test on (together with --forceExit)? Jest version etc.

I did a test in this project with --forceExit enabled and the test report was successfully generated.

[Hargne]

There is a potential fix for this issue in v2.0.0 - see #33

[zeevrosental]

Thank you very much!! I will see if it works for me :-) On Feb 19, 2018 13:30, "Johan Hargne" <[email protected]> wrote: There is a potential fix for this issue in v2.0.0 - see #33 <#33> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#19 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APccsNpR5a5-eFO6_0Oky9Zie1Z4C91Jks5tWVtPgaJpZM4Q25mG> .

[Hargne]

@zeevrosental v2.0.0 has now been released. I will mark this issue as resolved for now.