Nick Tomlin

The issue here is that the path in the stacktrace (which is what flake uses to choose what to re-run) is a ts one and not a js one: ```...

@sjmckinney that would be helpful, please share it if you still have it

thanks for this. I'm currently in a busy season at work and at home so I may not get to look at it for some time. I'd welcome a pull...

Ah this definitely seems like a bug. Thank you for the thorough issue! We could go with the approach you've suggested and just document that users _must_ pass the config...

Agreed; I think the best universal solution here is to write a custom reporter/logger for each framework and just consume our own output instead of trying to parse through the...

Could you provide some context on this pull request? I'm not sure I understand the use case. Thanks!

Apologies for the late reply. It looks like the parser is picking up two files: ``` # one /var/lib/jenkins/jobs/workplace-frontend-K8s/jobs/workplace-ci-feature/branches/IncreasingBrowserStackTests/workspace/cucumber/features/retirementage.feature # two cucumber/features/retirementage.feature ``` Without seeing more of the logs and...

@Trisha1212 I'm confused by your output. I see multiple invocations of `npm test` and there are multiple parsers being used here: ``` Using standard to parse output Re-running tests: test...

@Trisha1212 I'm confused by your output. I see multiple invocations of `npm test` and there are multiple parsers being used here: ``` Using standard to parse output Re-running tests: test...

@Trisha1212 As @surendraJ mentions, the multi parser is looking for output to attempt to match specs being run against any failures. First it looks for 1. Look for `------------------------------------` lines...