Disabled jcheck in all build-infra repos

Kelly O'Hair kelly.ohair at oracle.com
Thu Nov 10 06:07:15 PST 2011


Thanks for doing this. The server side was supposed to disable jcheck for these repos.

Did you check with John Coomes?  Or have you been given a set of golden keys to the Mercurial server area? ;^)

-kto

On Nov 10, 2011, at 7:31 AM, Robert Ottenhag wrote:

> Hi,
> 
> I have now explicitly disabled jcheck for all build-infra repos since some of the recent changes in build-infra/jdk7 made jcheck fail when trying to pull and update. The disabling was done on the server by removing the directory ".jcheck" in the root of each repository, as specified in the jcheck.py header documentation.
> 
> Alternative solutions such as disabling it locally in each $repo/.hg/hgrc file (overriding jcheck=...) or the global ~/.hgrc file where considered but rejected. The former needs to applied for each cloned build-infra repo, and the latter will also disable jcheck for any other standard Open or Closed JDK repo that actually requires it.
> 
> Also note that jcheck was never intended to be run on the build-infra repos in the first place, allowing free form commits and rapid development without bug IDs, as the changes are never intended to be directly committed upstream, but selectively ported.
> 
> The fix was separately reapplied to all build-infra repos (no, it was not merged...), including build-infra/{jdk7, jdk7-extra, jdk7-modules, jdk8}.
> 
> Thanks
> 
> /Robert
> 
> -- 
> Oracle
> Robert Ottenhag | Senior Member of Technical Staff
> Phone: +46850630961 | Fax: +46850630911 | Mobile: +46707106161
> Oracle Java HotSpot Virtual Machine
> ORACLE Sweden | Folkungagatan 122 | SE-116 30 Stockholm
> 
> Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746
> 
> Green Oracle
> 
> Oracle is committed to developing practices and products that help protect the environment
> --
> 
> 




More information about the build-infra-dev mailing list