Skip to content
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

empty PIT mutation report #2

Open
mnagel opened this issue Feb 12, 2014 · 13 comments
Open

empty PIT mutation report #2

mnagel opened this issue Feb 12, 2014 · 13 comments

Comments

@mnagel
Copy link

mnagel commented Feb 12, 2014

Dear Edward and other readers,

I am using this plugin, but I get an empty PIT mutation report.
In the console output I see the following:

...

--------------------------------------------------------------------------------
> org.pitest.mutationtest.engine.gregor.mutators.IncrementsMutator
>> Generated 27 Killed 10 (37%)
> KILLED 8 SURVIVED 4 TIMED_OUT 2 NON_VIABLE 0 
> MEMORY_ERROR 0 NOT_STARTED 0 STARTED 0 RUN_ERROR 0 
> NO_COVERAGE 13 
--------------------------------------------------------------------------------
> org.pitest.mutationtest.engine.gregor.mutators.NegateConditionalsMutator
>> Generated 834 Killed 461 (55%)
> KILLED 461 SURVIVED 80 TIMED_OUT 0 NON_VIABLE 0 
> MEMORY_ERROR 0 NOT_STARTED 0 STARTED 0 RUN_ERROR 0 
> NO_COVERAGE 293 
--------------------------------------------------------------------------------

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:19.069s
[INFO] Finished at: Wed Feb 12 17:15:40 CET 2014
[INFO] Final Memory: 25M/73M
[INFO] ------------------------------------------------------------------------

[JENKINS] Archiving /var/lib/jenkins/jobs/IDM-Adapter-Mutations/workspace/pom.xml to ***snip***/0.0.1-SNAPSHOT/idma-war-0.0.1-SNAPSHOT.pom
channel stopped
Looking for PIT reports in /var/lib/jenkins/jobs/***snip***/workspace
Publishing mutation report: /var/lib/jenkins/jobs/***snip***/workspace/target/pit-reports/201402121712/mutations.xml
Kill ratio is NaN% (0  0)
Build step 'Record Pit mutation testing report' changed build result to FAILURE
Sending e-mails to: ***snip***
Finished: FAILURE

Any idea what is going wrong here?

Best Regards
Michael

@edwardwe7
Copy link
Owner

It's hard to say. Actually I've done quite a bit of work on a vastly improved version of the plugin but it's hard to find the time to finish it. Anyway, perhaps you could send me a copy of the mutation report xml output and I can see whether there's a parser issue? My email is edward.kimber@gmail.com

@mnagel
Copy link
Author

mnagel commented Feb 14, 2014

Dear Edward, I sent you an email with the report. Thank you very much!

@mnagel
Copy link
Author

mnagel commented Feb 19, 2014

Hi Edward,

did you have a chance to analyse the report?

Thank you very much,
Michael

@ekimber
Copy link
Collaborator

ekimber commented Feb 25, 2014

Hi Michael,
The report is fine so it should work. Perhaps it's a configuration problem.
I'm going to update the plugin soon, I'll let you know when that happens.
Ed

@ekimber
Copy link
Collaborator

ekimber commented Mar 1, 2014

I updated my pit release to 0.32 and reproduced the problem. Have released a new version with the fix in it.

@ekimber ekimber closed this as completed Mar 1, 2014
@geeknitin
Copy link

geeknitin commented Jun 13, 2016

Hi,

I am also facing the same issue. Can you please let us know how you were able to fix this issue?
Please let me know I am blocked on this.

Looking for PIT reports in /data/jenkins/workspace/microservice-maven-proj
Publishing mutation report: /data/jenkins/workspace/microservice-maven-proj/app/target/pit-reports/mutations.xml
Kill ratio is NaN% (0 0)
Build step 'Record Pit mutation testing report' changed build result to FAILURE
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE


This is mutations.xml file

App.javacom.xyz.AppgetName()Ljava/lang/String;12org.pitest.mutationtest.engine.gregor.mutators.ReturnValsMutator4com.xyz.AppTest.testGetToday(com.xyz.AppTest)mutated return of Object value for com/xyz/App::getName to ( if (x != null) null else throw new RuntimeException ) App.javacom.xyz.Appmain([Ljava/lang/String;)V8org.pitest.mutationtest.engine.gregor.mutators.VoidMethodCallMutator12removed call to java/io/PrintStream::println

@ekimber
Copy link
Collaborator

ekimber commented Jun 15, 2016

Hi, sorry I'm kind of busy at the moment. I'll look into it when I can. What version of the plugin do you have?

@ekimber ekimber reopened this Jun 15, 2016
@Younusmohammed
Copy link

Hi all.. i am also facing the same issue like Mr.mnagel have. do we have any solution on how to configure the pitmutation report in jenkins. i am able to get the reports in index.html form. but want to generate report with jenkins build success.

@emlun
Copy link

emlun commented Jan 11, 2017

I have the same issue using version 1.0-13 of the plugin and pitest version 1.1.10 (via gradle-pitest-plugin).

@cosminstirbu
Copy link

I have the same issue. I have checked out the latest tag pitmutation-1.0-15 from here https://github.com/jenkinsci/pitmutation-plugin/releases, built the .hpi and I also receive Kill ratio is NaN% (0 0) in the console :(

@OleksiiBondar
Copy link

We have similar issue. Is anyone looking into this?

@rodripv
Copy link

rodripv commented Jun 20, 2017

I made a pull request for the latest pit-mutation jenkinsci#9

Hope it helps

@gigaSproule
Copy link

gigaSproule commented Oct 5, 2017

It would be great if the PR could be merged in as that solves my problem.

For anyone who is interested, I've managed to merge in all of the outstanding branches into 1 repo. I'm more than happy to open up a PR into the JenkinsCI one, but it looks rather large (unsurprisingly) and I don't believe it will ever get merged in as the others haven't yet...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants