From dev-return-29794-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Sun Oct 14 04:43:21 2007 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 7536 invoked from network); 14 Oct 2007 04:43:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Oct 2007 04:43:21 -0000 Received: (qmail 81685 invoked by uid 500); 14 Oct 2007 04:43:08 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 81660 invoked by uid 500); 14 Oct 2007 04:43:07 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 81651 invoked by uid 99); 14 Oct 2007 04:43:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Oct 2007 21:43:07 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of smallsmallorgan@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO py-out-1112.google.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Oct 2007 04:43:11 +0000 Received: by py-out-1112.google.com with SMTP id u77so2470225pyb for ; Sat, 13 Oct 2007 21:42:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=p0o7x1Ta9LHkaFUFi9EuJWdmsJOFN5Rt7WqSoghBG78=; b=dXDTo2wnlbT3tOKHrs8bAwsF67YlN3JdxIJAQwtDKLpv1tZtzt+SkJOHQNpKKIYIi10XUjt/aCg32KYW1FwzIAZ4Zl6zcrYtTbsYjecGOCym0ZYK4dAuruuT51eqyxXxa4NeVaXn4cLSFJ35wDIHhKr96Hvkpi2n5gPie3QhEoQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Et61oYSkNVEwRk3eV0HmkBSyPEoO6KypnVXir6bE0Yjw0tfDB9g3C3eKxApFTejZhX4qCU5SfFp2/Y+Jaukom+lt5Lp/8Yxgc9e7oB3bQQBoS7Lh5Fg4P0J07qRTu9xTwrRM8ucKQ0juzQMvyDF64QcYndRO5MEbslKOJLE0egE= Received: by 10.65.153.10 with SMTP id f10mr9913973qbo.1192336969392; Sat, 13 Oct 2007 21:42:49 -0700 (PDT) Received: by 10.65.61.12 with HTTP; Sat, 13 Oct 2007 21:42:49 -0700 (PDT) Message-ID: <473c46620710132142v457b7365s8db8df12604adf37@mail.gmail.com> Date: Sun, 14 Oct 2007 12:42:49 +0800 From: "Spark Shen" To: dev@harmony.apache.org Subject: Re: [buildtest][coverage] A new emma instrument adaptor for BTI 2.0 In-Reply-To: <94d710af0710112355xedb1881g45bb0d73e3f1030d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12376_19691777.1192336969384" References: <94d710af0710112355xedb1881g45bb0d73e3f1030d@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_12376_19691777.1192336969384 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I like this coverage report tool very much, especially after I read the detailed wiki page. Another candidate place for publishing this information is our blog[1]. We can add more charts and/or statisics there. AFAIK, customizing emma is not so trivial a work, and it is worthful to share more about it. Or will it also be a news to publish in our home page? Another thought: So far, we have many different test suites. Such as performance test suite[2], coverage test report, unit test suite, etc. How about we also add a link for coverage test report and unit test report like performance suite in harmony website. We can have a column called 'Quanlity Assurance' under 'Development', which includes many different test results - perfomance, unit test, coverage report etc. [1]http://apache-harmony.blogspot.com/ [2]http://harmony.apache.org/performance.html 2007/10/12, Sean Qiu : > > Hi, guys > > I have report a new jira[1] for test coverage issues. > As we have discussed earlier, this adaptor will do: > > 1. Maintain a copy of wanted jre to run test for generating coverage > report > 2. Instrument the library classes except some key classed that emma will > make use of. > 3. Add the instrumented classes and customized emma.jar [2] into the > bootstrap classpath. > > Within this adaptor, we can get a runnable instrumented jre for testing, > it > will generate emma meta files to get coverage report. > There is no need to do any more configurations when using the instrumented > jre. > > --------------- > Archive Content > --------------- > > This patch contains scripts for instrumenting a jre for generating > coverage > report. > The directories structure within BT trunk directory is as follows: > > +/ > |-+adaptors/ - scripts connecting test suites to BTI (called "adaptors") > | | > | |-+emma_instrument/ - emma_instrument suite adaptor directory > | | > | |--adaptor.xml - emma_instrument suite adaptor > | | > | |--parameters.xml - parameters file > | | > | |--EMMA.BTI.README.txt - this readme file > | > |-+tests/ - configuration files for customized emma instrumenting > | > |-+muave_test/ - emma_instrument configure directory > | > |--bootclasspath.properties - customized file to include instrumented > classes and emma.jar to bootstrap classpath > | > |--kernel.list - the list file of kernel classes which used by emma > when instrumenting > | > |--all.api.list - the list file of all the public API classes > | > |--exclude.api.list - the list file of classes in luni-kernel.jar and > security-kernel.jar, those classes can not be collected, > we must exclude them. > Those > classes are NOT the kernel classes mentioned befor > > ------------ > Known issues > ------------ > > 1. The drlvm can not load the instrumented classes, it will throw an > error: > java/lang/ClassFormatError : com/vladium/emma/rt/RT : invalid magic > Using j9vm is OK to generate emma files to get coverage report. > > I will try to find out why instrumented jre with drlvm cannot run the > test, > any help from drlvm gurus are prefered. > > [1] https://issues.apache.org/jira/browse/HARMONY-4932 > [2] http://wiki.apache.org/harmony/coverageEMMA > > -- > Sean Qiu > China Software Development Lab, IBM > -- Spark Shen China Software Development Lab, IBM ------=_Part_12376_19691777.1192336969384--