Skip to content


Subversion checkout URL

You can clone with
Download ZIP


publish JUnit test result report failing with cucumber and rspec tests #60

justlanded opened this Issue · 5 comments

3 participants


I am using hudson version 2.2.0 and ruby version 1.9.2p290 with your lastest version of ci_reporter. I am running my cucumber and spec tests with the ci:setup:cucumber and ci:setup:rspec respectively. The tests run and the reports are generated.

However when I specify the Publish JUnit test result report and specify the Test report XMLs as features/reports/.xml,spec/reports/xml, Hudson reports the following exception:

Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
at hudson.tasks.junit.CaseResult.getPackageName(
at hudson.tasks.junit.TestResult.tally(
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(
at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(
at hudson.FilePath.act(
at hudson.FilePath.act(
at hudson.tasks.junit.JUnitParser.parse(
at hudson.tasks.junit.JUnitResultArchiver.parse(
at hudson.tasks.junit.JUnitResultArchiver.perform(
at hudson.tasks.BuildStepMonitor$1.perform(
at hudson.model.AbstractBuild$AbstractRunner.perform(
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(
at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(
at hudson.model.Build$RunnerImpl.post2(
at hudson.model.AbstractBuild$
at hudson.model.ResourceController.execute(

Can you please tell me what I need to do to get this working properly.

Best regards,



I haven't heard of that error before. Can you navigate through the workspace for the build and see if the xml files did in fact get generated properly? If so, it might be a Hudson issue. Or else there might be content in the report xml files that Hudson does not like. Maybe you can investigate what in the report xml might be causing the problem?


Great, thanks for reporting back, and glad you solved the issue.

@nicksieger nicksieger closed this

I think I should be adding this information somewhere, like the README or the wiki... It tripped me up so badly, and I was so stoked when I found this issue. Where would the right place be? I'd be happy to just save others the pain and realize the value of this gem....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.