-
Notifications
You must be signed in to change notification settings - Fork 152
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
Failure in Jenkins with recently released 1.23.2 #106
Comments
@IdanAdar Can you provide more context?
|
Having a similar issue on CircleCI with mocha 6.2.0, circleci/node:10 and nyc. |
Node 12.13, mocha 6.2.2. |
And the problem appears to be that no result file is produced? Sent with GitHawk |
We see the same on Circle CI. It seems no result file is produced. |
Same issue here, Node 12, Mocha 7 fresh npm install on the repo installs mocha 5 and all tests pass, if you bump that to mocha6+ the tests fail. |
Facing the same issue when working with mocha-multi-reporters. 1.23.1 works well. |
I have similar issue. With v1.23.1, using the options, It seems it is related to the recent change in this line: https://github.com/michaelleeallen/mocha-junit-reporter/blob/master/index.js#L43 |
We are seeing the same issue -- this reporter stopped respecting our reporter-options on 1.23.2 . Downgrading to 1.23.1 resolved the problem for us. We're on mocha 7.0.0, node 12.4.0 |
Same issue with CodeceptJS 2.4.1, NodeJS v10.18.1, mocha@6.2.2, mocha-junit-reporter@1.23.2. |
Sorry for the heartache. I’ll see if I can–at least–get a patch release out today that reverts the changes that went in over the weekend while I look into the root cause Sent with GitHawk |
@clayreimann were you able to work out patch? |
This should be resolved with 1.23.3 |
Starting 1.23.2 after tests have passed/failed in Jenkins the following error is printed:
If going back to 1.23.1, everything works as expected, so looks like one of these changes created a regression: v1.23.1...master
@clayreimann You seem to be the one who pushed code most recently.
@michaelleeallen FYI.
The text was updated successfully, but these errors were encountered: