running tests from make causes spurious repo changes

Maurizio Cimadamore maurizio.cimadamore at
Tue Sep 26 11:10:14 UTC 2017

On 26/09/17 07:13, Alan Bateman wrote:
> On 25/09/2017 21:35, Maurizio Cimadamore wrote:
>> On 25/09/17 20:58, Alan Bateman wrote:
>>> On 25/09/2017 20:11, Jonathan Gibbons wrote:
>>>> Erik,
>>>> 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.
>>> Something fishy in this thread as these tests have historically not 
>>> changed the permissions of these libraries. So I'm curious how they 
>>> were run, I wonder in case they were changed by a make file instead.
>> make test TEST=jdk_lang
>> AFAIK, this should be the correct way of invoking tests from make?
> I assume this make file must be running chmod, not the tests 
> themselves as otherwise this issue would have been noticed a long time 
> ago. I suspect many people run jtreg directly in their local 
> environment rather than the make file.
Note that I've been running tests this way over the last 2-3 years, and 
this only started to happen after the move to consolidated repo. That's 
why I correlated the two things.

> In any case, these older tests predate build test support for 
> compiling native code and probably should be migrated anyway.
> -Alan

More information about the build-dev mailing list