From chris.hegarty at oracle.com Sun Jan 13 01:07:13 2013 From: chris.hegarty at oracle.com (Chris Hegarty) Date: Sun, 13 Jan 2013 09:07:13 +0000 Subject: jcheck and the ProblemList Message-ID: <50F27941.4010109@oracle.com> Hi toolers, Is there an appetite to support a request to update jcheck to add ProblemList updates to the list of exceptional changesets, like merge and tags? The ProblemList is a file that lives in the jdk repository, test/ProblemList.txt. It contains a list of tests with known issues, and links the bug tracking the test issue. Currently, a test failure requires at least two bugs, one to track the actual test failure and another to put it on the ProblemList ( until the test can test issue can be resolved ). What I am proposing is that a changeset, containing an update to a single file, test/problemList.txt, would be acceptable with relaxed enforcement of the comment style, i.e. bug no. and reviewer. -Chris. From weijun.wang at oracle.com Sun Jan 13 05:04:26 2013 From: weijun.wang at oracle.com (Wang Weijun) Date: Sun, 13 Jan 2013 21:04:26 +0800 Subject: jcheck and the ProblemList In-Reply-To: <50F27941.4010109@oracle.com> References: <50F27941.4010109@oracle.com> Message-ID: I totally agree. We can restrict the comment to a constant string. Max ?? Jan 13, 2013??5:07 PM??Chris Hegarty ?????? > Hi toolers, > > Is there an appetite to support a request to update jcheck to add ProblemList updates to the list of exceptional changesets, like merge and tags? > > The ProblemList is a file that lives in the jdk repository, test/ProblemList.txt. It contains a list of tests with known issues, and links the bug tracking the test issue. Currently, a test failure requires at least two bugs, one to track the actual test failure and another to put it on the ProblemList ( until the test can test issue can be resolved ). > > What I am proposing is that a changeset, containing an update to a single file, test/problemList.txt, would be acceptable with relaxed enforcement of the comment style, i.e. bug no. and reviewer. > > -Chris. From John.Coomes at oracle.com Wed Jan 23 16:45:19 2013 From: John.Coomes at oracle.com (John Coomes) Date: Wed, 23 Jan 2013 16:45:19 -0800 Subject: jcheck review request (xs) - blacklist update Message-ID: <20736.33823.245595.230376@oracle.com> I'd appreciate a review of this simple addition to the jcheck blacklist: http://cr.openjdk.java.net/~jcoomes/tools/jcheck/blacklist-20130123/ -John From iris.clark at oracle.com Wed Jan 23 21:41:19 2013 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 23 Jan 2013 21:41:19 -0800 (PST) Subject: jcheck review request (xs) - blacklist update In-Reply-To: <20736.33823.245595.230376@oracle.com> References: <20736.33823.245595.230376@oracle.com> Message-ID: Looks fine to me. iris -----Original Message----- From: John Coomes Sent: Wednesday, January 23, 2013 4:45 PM To: hg-tools-dev at openjdk.java.net Subject: jcheck review request (xs) - blacklist update I'd appreciate a review of this simple addition to the jcheck blacklist: http://cr.openjdk.java.net/~jcoomes/tools/jcheck/blacklist-20130123/ -John From john.coomes at oracle.com Thu Jan 24 14:14:15 2013 From: john.coomes at oracle.com (john.coomes at oracle.com) Date: Thu, 24 Jan 2013 22:14:15 +0000 Subject: hg: code-tools/jcheck: Blacklist bad fix for 8006611 Message-ID: <20130124221415.EEF4747536@hg.openjdk.java.net> Changeset: ce5e03ccbf6b Author: jcoomes Date: 2013-01-23 16:29 -0800 URL: http://hg.openjdk.java.net/code-tools/jcheck/rev/ce5e03ccbf6b Blacklist bad fix for 8006611 ! jcheck.py From john.coomes at oracle.com Thu Jan 24 14:14:19 2013 From: john.coomes at oracle.com (john.coomes at oracle.com) Date: Thu, 24 Jan 2013 22:14:19 +0000 Subject: hg: code-tools/jcheck/dist: jcheck ce5e03ccbf6b 2013-01-23 16:29:50 -0800 Message-ID: <20130124221419.424BB47537@hg.openjdk.java.net> Changeset: 3aa604e05212 Author: jcoomes Date: 2013-01-23 16:29 -0800 URL: http://hg.openjdk.java.net/code-tools/jcheck/dist/rev/3aa604e05212 jcheck ce5e03ccbf6b 2013-01-23 16:29:50 -0800 ! jcheck.py