-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Last test result not being published #12
Comments
@scottcrowesai can you please enable logLevel to trace in the elk-reporter file https://github.com/mpahuja/mocha-elk-reporter/blob/master/elk-reporter.js#L5 and see if the request is actually going out to your elk cluster |
Attached is the output from our tests (with some minor information scrubbing). Looks like the first test fires the request but doesn't get the response till the second test has started and the second test doesn't wait for the response. |
Sorry about the delay in responding but I able to reproduce the issue with a ES 6.7 but not with older version of ES. I will look into this issue soon. Thanks for reporting. @scottcrowesai |
Just started working for me without updating any of my test code. I'm guessing our infrastructure team updated ES to a version without the problem. 🤷♂️ |
What version of ES are you using? |
Looks like |
I have a project using Cypress.io at 3.1.5, Mocha at 4.0.1 and latest of this project (2.0.1).
When running tests all but the last spec file ran are being published as expected.
I thought it was potentially an issue with the process closing before the final result is done, however adding a 30 second wait after tests are complete before the process exits did not resolve the issue.
I'm seeing this using
mocha-elk-reporter
as the only reporter or withmocha-multi-reporters
adding reporting forspec
andmocha-junit-reporter
. The JUnit reporter is correctly reporting the final Spec.The text was updated successfully, but these errors were encountered: