running tests from make causes spurious repo changes

Martin Buchholz martinrb at google.com
Mon Sep 25 18:47:56 UTC 2017


It should be standard practice for whoever does systematic jtreg testing to
do it occasionally with the jdk sources mounted in a read-only file system,
and ensure all the tests still pass.

On Mon, Sep 25, 2017 at 4:54 AM, Maurizio Cimadamore <
maurizio.cimadamore at oracle.com> wrote:

>
>
> On 25/09/17 12:53, Erik Joelsson wrote:
>
>> I couldn't agree with you more, but AFAIK, this behavior is in the tests
>> themselves and not something the build is doing.
>>
> I see - for the records, I got this when running the test group jdk_lang
>
> Maurizio
>
>
>> /Erik
>>
>>
>> On 2017-09-25 13:33, Maurizio Cimadamore wrote:
>>
>>> Hi,
>>> if I try to run tests from make, after the test run an 'hg status'
>>> reveal the following 'changes':
>>>
>>> M test/jdk/java/nio/channels/spi/SelectorProvider/inheritedCha
>>> nnel/lib/linux-i586/libLauncher.so
>>> M test/jdk/java/nio/channels/spi/SelectorProvider/inheritedCha
>>> nnel/lib/solaris-amd64/libLauncher.so
>>> M test/jdk/java/nio/channels/spi/SelectorProvider/inheritedCha
>>> nnel/lib/solaris-sparcv9/libLauncher.so
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/freebl3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/nspr4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/nss3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/nssckbi.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/nssdbm3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/nssutil3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/plc4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/plds4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/softokn3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/sqlite3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-amd64/ssl3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/freebl3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/nspr4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/nss3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/nssckbi.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/nssdbm3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/nssutil3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/plc4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/plds4.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/softokn3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/sqlite3.dll
>>> M test/jdk/sun/security/pkcs11/nss/lib/windows-i586/ssl3.dll
>>>
>>> What's up? Shouldn't this stuff end up in build folder?
>>>
>>> Cheers
>>> Maurizio
>>>
>>>
>>
>



More information about the build-dev mailing list