Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <32677191.1173452364335.JavaMail.root@brutus>
Date: Fri, 9 Mar 2007 06:59:24 -0800 (PST)
From: "weldon washburn (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-3336) documentation -- need instructions
 on how to run HUT tests, Eclipse hello world test,  regression tests in
 general
In-Reply-To: <20357338.1173412824271.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479606 ] 

weldon washburn commented on HARMONY-3336:
------------------------------------------

Some suggestions on running pre-commit tests.  Currently running these tests is way too many clicks.

1.
single click do-it-all button ("build clean; build; build test_whatever_we_decide_the_precommit_criteria_is" )
2.
some sort of mechanical parser to dig through the very hard to read output of a build failure and tell the committer in simple terms exactly where the problem(s) are
3.
the " build" should have the following command line (and/or gui pulldowns)
         a.  build just DRLVM
         b.  build just classlibs
         c.  build both drlvm/classlibs
4.
the "build clean" should have the same choices (clean drlvm, classlibs, both)
5.
The Harmony "pre-commit criteria team" is to be responsible for updating the config and exclude files that actually select which tests are run.  The average committers and developers should modify these files on their local drives when they need to work around local problems and should refrain from updating svn HEAD. 


> documentation -- need instructions on how to run HUT tests, Eclipse hello world test,  regression tests in general
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3336
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3336
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: all platforms
>            Reporter: weldon washburn
>
> there needs to be one document that shows how to run all the regression tests and how to decypher the results.  For example, "build test" gives very vague output.  Is this because "build test" needs to be run from Eclipse framework?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.