<div dir="ltr">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.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 25, 2017 at 4:54 AM, Maurizio Cimadamore <span dir="ltr"><<a href="mailto:maurizio.cimadamore@oracle.com" target="_blank">maurizio.cimadamore@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 25/09/17 12:53, Erik Joelsson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I couldn't agree with you more, but AFAIK, this behavior is in the tests themselves and not something the build is doing.<br>
</blockquote></span>
I see - for the records, I got this when running the test group jdk_lang<span class="HOEnZb"><font color="#888888"><br>
<br>
Maurizio</font></span><div class="HOEnZb"><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
/Erik<br>
<br>
<br>
On 2017-09-25 13:33, Maurizio Cimadamore wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
if I try to run tests from make, after the test run an 'hg status' reveal the following 'changes':<br>
<br>
M test/jdk/java/nio/channels/spi<wbr>/SelectorProvider/inheritedCha<wbr>nnel/lib/linux-i586/<wbr>libLauncher.so<br>
M test/jdk/java/nio/channels/spi<wbr>/SelectorProvider/inheritedCha<wbr>nnel/lib/solaris-amd64/<wbr>libLauncher.so<br>
M test/jdk/java/nio/channels/spi<wbr>/SelectorProvider/inheritedCha<wbr>nnel/lib/solaris-sparcv9/<wbr>libLauncher.so<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/freebl3.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/nspr4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/nss3.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/nssckbi.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/nssdbm3.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/nssutil3.<wbr>dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/plc4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/plds4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/softokn3.<wbr>dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/sqlite3.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-amd64/ssl3.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/freebl3.dl<wbr>l<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/nspr4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/nss3.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/nssckbi.dl<wbr>l<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/nssdbm3.dl<wbr>l<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/nssutil3.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/plc4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/plds4.dll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/softokn3.d<wbr>ll<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/sqlite3.dl<wbr>l<br>
M test/jdk/sun/security/pkcs11/n<wbr>ss/lib/windows-i586/ssl3.dll<br>
<br>
What's up? Shouldn't this stuff end up in build folder?<br>
<br>
Cheers<br>
Maurizio<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>