From dev-return-26934-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Fri May 11 13:23:28 2007 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 48915 invoked from network); 11 May 2007 13:23:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 May 2007 13:23:27 -0000 Received: (qmail 10270 invoked by uid 500); 11 May 2007 13:23:31 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 10242 invoked by uid 500); 11 May 2007 13:23:31 -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 10229 invoked by uid 99); 11 May 2007 13:23:31 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 06:23:31 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of alexei.zakharov@gmail.com designates 64.233.184.229 as permitted sender) Received: from [64.233.184.229] (HELO wr-out-0506.google.com) (64.233.184.229) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 May 2007 06:23:24 -0700 Received: by wr-out-0506.google.com with SMTP id i31so1066462wra for ; Fri, 11 May 2007 06:23:03 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:content-transfer-encoding:content-disposition:references; b=slK7ggf06tBZJsMXyJzjs3HWr+0c0ah4EGYowSGrfIS+CACu/g8ND8M0HyMQPuIbK4CegkYSLk7dN54JfFD2WqJNb9lAtxbJE1pMXPhXfm3ZIlILGNuyxio0YGO9kuzr3RmOUjo/IZDMoEeAYcmWDaxi1j/11xv9z0zH5eCdBSY= 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:content-transfer-encoding:content-disposition:references; b=QEee87euvtVPX1BVVoe7SEH7Th38LPfG+nlW8YC7GuoRLWD+h9KTLsLiJcGOGAv1B06QcpHd4I98N1DuXmI11oKlqC8nKv5QFu/xTheS1i9jYyQHSALgx5Z4v/8ijrlxb1SWZ5M99svqk4YbZXdUjwWg+gIfopzRxwpCZiJn+G4= Received: by 10.78.132.2 with SMTP id f2mr825861hud.1178889782162; Fri, 11 May 2007 06:23:02 -0700 (PDT) Received: by 10.78.121.15 with HTTP; Fri, 11 May 2007 06:23:02 -0700 (PDT) Message-ID: <2c9597b90705110623y5cce5071xd0ae998ae717815b@mail.gmail.com> Date: Fri, 11 May 2007 17:23:02 +0400 From: "Alexei Zakharov" To: dev@harmony.apache.org Subject: Re: [drlvm][build files] Does anyone know how to cause only cunit.test to be executed? In-Reply-To: <4dd1f3f00705100927l2e65c74vcbd8b04014b60dfa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4dd1f3f00705081055m513b856ei68521e26feef4d0d@mail.gmail.com> <2c9597b90705090524v1c92df62hffbc68345e87e09@mail.gmail.com> <4dd1f3f00705090716o7d2d9728oaa9e648c907a1740@mail.gmail.com> <4dd1f3f00705100927l2e65c74vcbd8b04014b60dfa@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org > The original developers of the C unit test must > have had some way of running individual tests. Maybe they can donate this > scripting code?? This can take too long time to wait for them. For now I've added new top level target "cunit.test" at r537186. The test run take less than two minutes on my machine. Please check if it solves your problem. Regards, 2007/5/10, Weldon Washburn : > On 5/10/07, Alexey Varlamov wrote: > > > > Hi Weldon, > > > > You've got wrong impression somehow, ehwa and cunit tests have > > absolutely no relation and/or dependency. Currently cunit tests are > > part of the top-level joint target "test", but I have no idea why > > there is no standalone target for them. > > > Most likely I am confused by the testing scripts. I really do not > understand them. > > Another point, do your tests really fit into unit testing concept? > > > Actually, its not my tests. The problem is that the existing tests fail to > link when I add a call to gc_force_gc() from the Thread Manager code. > Somehow I need to add an empty gc_force_gc() { } stub to the C unit test > framework. But first I would like a quick way to run the C unit tests. > > > If > > they involve several components, maybe just put them into different > > suite? > > > hmm... it would be nice to avoid rewriting the C unit thread tests. Maybe > there is a simpler way. The original developers of the C unit test must > have had some way of running individual tests. Maybe they can donate this > scripting code?? > > 2007/5/9, Weldon Washburn : > > > On 5/9/07, Alexei Zakharov wrote: > > > > > > > > Hi Weldon, > > > > > > > > Looks like you can't do exactly what you want with current build > > > > scripts. Or at least I don't know an easy way. I suppose we can add a > > > > top-level target like thread.test for running these tests separately > > > > if you think it makes sense. > > > > > > > > > How soon can thread.test be added? It turns out that I need to be able > > to > > > call gc_force_gc() from jthread.lib. The cunit.test fails because > > > jthread.lib hits an unresolved external reference (gc_force_gc) when > > linking > > > with the cunit test framework. This should be an easy thing to fix once > > the > > > build/test cycle is shortened. The current build/test cycle for "build > > > ehwa.test" is more than 20 minutes currently. > > > > > > Looking at the big picture, what did the original test developers do to > > > solve the above problems? Maybe this code has already been developed > > and > > > simply not yet donated?? Does anybody know? > > > > > > > > > Regards, > > > > > > > > 2007/5/8, Weldon Washburn : > > > > > All, > > > > > From "build test2" output, it looks like cunit.test is called > > > > (indirectly) > > > > > by ehwa.test. "build ehwa.test" works fine but takes a really long > > time > > > > to > > > > > run. I would like to quickly run just the tests located in the > > > > > working_vm/vm/tests/unit/thread directory. Can the build experts > > give > > > > > suggestions on how to do this. > > > > > > > > > > Thanks -- Alexei Zakharov, Intel ESSD