harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess" <mark.hind...@googlemail.com>
Subject Re: classlib test suite status emails?
Date Tue, 11 Apr 2006 10:42:02 GMT
I've submitted a JIRA containing a fix that is something close to what
Stepan suggested.  Having module test targets append the name of the
module to a build/test_report/test.errors (or test.failures) and the
top level target fails if those files exist at the end of the run.

The diff to make this change would be so much easier if we'd refactor
the build files - perhaps as I suggested in HARMONY-293.  I'm going to
update this JIRA to fix it with respect to all the recent moves and
test additions but I'd be interested in peoples views on this in the
meantime.  I think refactoring will make life much easier.

-Mark.

On 4/11/06, Geir Magnusson Jr <geir@pobox.com> wrote:
>
>
> Mark Hindess wrote:
> > Yes.  I was using the failureproperty mechanism.  Trying to get this
> > property propogated back to the top level ant file was what I was
> > having trouble with.
> >
>
> I had the same problem.  I wanted the whole thing to halt on any
> failure, and it didn't work...  the top level ant script didn't pay
> attention...
>
>
> > Using a file as you suggest might help.  I'll give that a try shortly...
> >
> > Incidentally, I'm seeing 12 failures and 3 errors on r393111.  (And
> > there are typos - "mathc" should be "match" - in the failure messages
> > for java.security.cert testMatch and testClone.)
> >
> > Regards,
> >  Mark.
> >
> > On 4/11/06, Stepan Mishura <stepan.mishura@gmail.com> wrote:
> >> On 4/11/06, Mark Hindess wrote:
> >>
> >>> Stepan,
> >>>
> >>> I have another build running (but without notifications going to the
> >>> list) that runs:
> >>>
> >>> 1) build (with reference jdk)
> >>> 2) build with what we created with 1)
> >>> 3) test
> >>> 4) create classlists and compare with class load data for applications
> >>>    (tomcat, geronimo, continuum, etc.)
> >>> 5) generate JAPI results
> >>>
> >>> I'd like to fail this build at step 3, but I can't see an easy way to
> >>> get 'ant -f make/build.xml test' to run all tests and then fail if any
> >>> of the module test sub-targets had test failures.  I could parse the
> >>> output I suppose, but I'd rather get ant to propagate the junit tasks
> >>> failure property back up to the top level.  I've tried a couple of
> >>> things and none seem to work.  Any suggestions welcome.
> >>
> >>  Mark, did you try failureproperty parameter for junit task?
> >> We may add it to ant sub-targets to raise a flag, for example, create file "
> >> TESTS.FAILED" in the root,  when tests for some module fail. And in the end
> >> of tests suite run check whether this file exists on not.
> >>
> >> Thanks,
> >> Stepan.
> >>
> >>
> >> Regards,
> >>> Mark.
> >>>
> >>> On 4/11/06, Stepan Mishura <stepan.mishura@gmail.com> wrote:
> >>>> Hi,
> >>>>
> >>>> I've checked out at morning last updates, built the code base and run
> >>> the
> >>>> tests …and there are 24 tests failures!
> >>>>
> >>>> There are 9 tests failures in
> >>>> org.apache.harmony.tests.java.nio.channels.DatagramChannelTest – I
saw
> >>> these
> >>>> failures before from time to time. It seems that tests depend on some
> >>> race
> >>>> conditions because they may pass if I rerun them. Paulex, are these
> >>> tests
> >>>> passing for you?
> >>>>
> >>>> And there are new 15 test failures.  So now if I'll make a code update
> >>> or a
> >>>> bug fix how I can be 100% sure that I don't do any regression?
> >>>>
> >>>> Currently if a commit breaks the Harmony classlib build a notification
> >>> with
> >>>> subject: "[continuum] BUILD FAILURE: Classlib/linux.ia32" will be send
> >>> to
> >>>> harmony-commits mailing list. Is it possible to have the same for tests?
> >>> I
> >>>> mean that after completing automatic build the existing classlib tests
> >>> suite
> >>>> should be run. If there are failing tests then a report notification
> >>> with
> >>>> corresponding subject will be send.
> >>>>
> >>>> Thanks,
> >>>> Stepan Mishura
> >>>> Intel Middleware Products Division
> >>> --
> >>> Mark Hindess <mark.hindess@googlemail.com>
> >>> IBM Java Technology Centre, UK.
> >>>
> >>> ---------------------------------------------------------------------
> >>> Terms of use : http://incubator.apache.org/harmony/mailing.html
> >>> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >>>
> >>>
> >>
> >> --
> >> ---------------------------------------------------------------------
> >> Terms of use : http://incubator.apache.org/harmony/mailing.html
> >> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >>
> >> Thanks,
> >> Stepan Mishura
> >> Intel Middleware Products Division
> >>
> >>
> >
> >
> > --
> > Mark Hindess <mark.hindess@googlemail.com>
> > IBM Java Technology Centre, UK.
> >
> > ---------------------------------------------------------------------
> > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>


--
Mark Hindess <mark.hindess@googlemail.com>
IBM Java Technology Centre, UK.

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message