running tests from make causes spurious repo changes

Jonathan Gibbons jonathan.gibbons at
Mon Sep 25 19:11:48 UTC 2017


It could be a feature of the build (i.e. test makefiles) to verify that 
no source-controlled files were modified in the course of a test run.

A related, secondary feature could be to make sure that no new files 
were written in directories containing source-controlled files (i.e. 
src, make, test, etc). Together, these checks could be combined by 
comparing the output of "hg status" before and after the test run.

Martin's suggestion to run on a read-only filesystem is also a good one, 
but maybe harder for most people to set up (e.g. on a laptop or Dev 
machine), so makefile checks would be nice.

-- Jon

On 9/25/17 4:53 AM, 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.
> /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/inheritedChannel/lib/linux-i586/
>> M 
>> test/jdk/java/nio/channels/spi/SelectorProvider/inheritedChannel/lib/solaris-amd64/
>> M 
>> test/jdk/java/nio/channels/spi/SelectorProvider/inheritedChannel/lib/solaris-sparcv9/
>> 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