Newman sends report summary and custom report after 180 sec and continues to run.

1. Newman Version (can be found via newman -v):3.9.x
2. OS details (type, version, and architecture):confirmed on Linux Mint and Mac
3. Are you using Newman as a library, or via the CLI? library
4. Did you encounter this recently, or has this bug always been there: recently
5. Expected behaviour: newman should report after the run is completed
6. Command / script used to run Newman: node script
7. Sample collection, and auxiliary files (minus the sensitive details):
8. Screenshots (if applicable):

When executing a script which runs newman and interprets the newman run, then sends a custom report to Testrail, we found that during the test run (180 sec into the run) newman triggers the cli reporter, which triggers our custom reporter, but the newman run continues to execute in CLI. This results in incomplete reports. Our collection is quite big with up to 13 different iterations and up to 2K assertions so it takes way longer than 180 sec to complete all iterations.

I found that this behavior is present in 3.9.x newman versions.

Rolling back to v3.8.3 fixed our issue!

Placed this issue here in hope that someone will find this to be the solution for their issue.

[bbartoni]

This is not an issue for me any longer, @kunagpal . after temporary roll-back to v3.8.3, we recently added explicit timeout: 120000 (which suites our needs, but still limits the exec), I then updated to newman -v 3.9.3 and been running without any problems to this day.

[kunagpal]

@shamasis Yes, that is also a possibility. We need to confirm the exact underlying cause.