lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4332) Integrate PiTest mutation coverage tool into build
Date Thu, 30 Aug 2012 05:54:07 GMT


Dawid Weiss commented on LUCENE-4332:

Greg, what's this responsible for:
+  <property name="pitest.threads" value="2" />

Is this test execution concurrency at JVM level? If so, it needs to be set to "1" because
tests won't support concurrent suites (too many static stuff lying around).

+        <!-- Java7 has a new bytecode verifier that _requires_ stackmaps to be present
in the
+             bytecode. Unfortunately a *lot* of bytecode manipulation tools (including pitest)
+             do not currently write out this information; for now we are forced to disable
+             in the jvm args -->

Both proguard and asmlib produce these I think. Just a note, I know it's probably not possible
to integrate in pi's toolchain without changes to its source code.

+        <script language="javascript"><![CDATA[

Will this require people to put rhino in ant's lib/ folder? If so, I'd just use an ugly property
value="-D..=${} -D..=${}..". Yours is very nice but an additional step is required which seems
an overkill?
> Integrate PiTest mutation coverage tool into build
> --------------------------------------------------
>                 Key: LUCENE-4332
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 4.1, 5.0
>            Reporter: Greg Bowyer
>            Assignee: Greg Bowyer
>              Labels: build
>         Attachments: LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch,
LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch, LUCENE-4332-Integrate-PiTest-mutation-coverage-tool-into-build.patch
> As discussed briefly on the mailing list, this patch is an attempt to integrate the PiTest
mutation coverage tool into the lucene build

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message