Failure in Jenkins with recently released 1.23.2

Question

Failure in Jenkins with recently released 1.23.2

IdanAdar opened this issue 5 years ago · 13 comments

Starting 1.23.2 after tests have passed/failed in Jenkins the following error is printed:

 139 passing (16m)


=============================== Coverage summary ===============================
Statements   : 89.09% ( 1053/1182 )
Branches     : 79.29% ( 356/449 )
Functions    : 89.82% ( 150/167 )
Lines        : 89.05% ( 1041/1169 )
================================================================================
[Pipeline] junit
Recording test results
No test report files were found. Configuration error?

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.

Answer 1 · 2020-01-12T14:19:37.000Z

@IdanAdar Can you provide more context?

What version of mocha?
What version of node?
Are you using other software (nyc, webpack, etc.)?
Can you provide a reproducible example project?
Are there other errors in the output?

Answer 2 · 2020-01-12T18:00:22.000Z

Having a similar issue on CircleCI with mocha 6.2.0, circleci/node:10 and nyc.

Answer 3 · 2020-01-12T19:18:23.000Z

Node 12.13, mocha 6.2.2.
This started the second 1.23.2 was released and is resolved if going back to 1.23.1.

Answer 4 · 2020-01-12T19:32:23.000Z

And the problem appears to be that no result file is produced?

_{Sent with GitHawk}

Answer 5 · 2020-01-12T20:00:04.000Z

We see the same on Circle CI. It seems no result file is produced.

Answer 6 · 2020-01-13T03:08:02.000Z

Same issue here, Node 12, Mocha 7
In my case the "No test report files were found" is misleading. It's creating a result file but it's using the default filename test-results.xml, we're using --reporter-options with a custom mochaFile but it's being ignored.

fresh npm install on the repo installs mocha 5 and all tests pass, if you bump that to mocha6+ the tests fail.

Answer 7 · 2020-01-13T09:31:39.000Z

Facing the same issue when working with mocha-multi-reporters. 1.23.1 works well.
Please also test with mocha-multi-reporters.

Answer 8 · 2020-01-13T14:57:18.000Z

I have similar issue. With v1.23.1, using the options, --reporter-options, with a custom mochaFile does not work. It is always creating the results xml in the root directory with default filename, test-results.xml.

It seems it is related to the recent change in this line: https://github.com/michaelleeallen/mocha-junit-reporter/blob/master/index.js#L43

Answer 9 · 2020-01-14T05:56:29.000Z

We are seeing the same issue -- this reporter stopped respecting our reporter-options on 1.23.2 . --reporter-option mochaFile=./build/test-results-unit.xml no longer works.

Downgrading to 1.23.1 resolved the problem for us.

We're on mocha 7.0.0, node 12.4.0

Answer 10 · 2020-01-14T12:23:54.000Z

Same issue with CodeceptJS 2.4.1, NodeJS v10.18.1, mocha@6.2.2, mocha-junit-reporter@1.23.2.
Configuration option mochaFile: "./output/result.xml" in CodeceptJS stopped working.
I had to downgrade to 1.23.1: npm i mocha-junit-reporter@1.23.1

Answer 11 · 2020-01-14T14:38:26.000Z

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}

Answer 12 · 2020-01-16T10:14:21.000Z

@clayreimann were you able to work out patch?

Answer 13 · 2020-01-16T14:03:29.000Z

This should be resolved with 1.23.3