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 Tue, 28 Aug 2012 20:05:07 GMT


Dawid Weiss commented on LUCENE-4332:

bq. toFacyDawidWeissSeedFormat

That's just a hex representation of eight bytes (unsigned long), nothing fancy.

bq. We should install a SecurityManager always and only allow files in build/test

I didn't cater for the presence of a security manager in the runner and it will probably break
things in the runner that will be tough to debug. Just a fair warning. You will probably have
to give the runner a policy of being able to do everything and it still may fail to run.

bq. also we should ask Dawid if each forked jvm can get its own sandbox'ed
in build/test:

They already do I think because tmpdir property is overridden with "." and cwd is set to J0/J1/J2/JN
under the test dir.
> 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,
> 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