buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <boisv...@intalio.com>
Subject Re: Build completes successfully on configuration failures and skipped tests
Date Mon, 10 Aug 2009 09:07:34 GMT
Can you create a Jira issue and attach a sample project that demonstrates
the issue?  (Or point me to it if it already exists)

alex


On Mon, Aug 10, 2009 at 12:41 AM, Martin Grotzke <
martin.grotzke@javakaffee.de> wrote:

> Hi,
>
> this is still an issue for us. Can anybody help with this?
>
> Cheers,
> Martin
>
>
> On Mon, 2009-07-27 at 11:12 +0200, Martin Grotzke wrote:
> > Hi,
> >
> > we have the issue, that the build completes successfully if with
> > configuration failures and skipped tests.
> >
> > This is the output of the test run (buildr clean test):
> >
> > ===============================================
> > ff-webapp
> > Total tests run: 55, Failures: 0, Skips: 55
> > Configuration Failures: 1, Skips: 66
> > ===============================================
> >
> > Completed in 29.550s
> >
> > (the shown output is just the summary for the run of one of the
> > subprojects).
> >
> > The configuration failure is e.g.
> >
> > FAILED CONFIGURATION: @BeforeClass setupIntegrationTest
> > com.google.inject.CreationException: Guice creation errors:
> >
> > 1) A binding to com.proj.core.common.UrlService was already configured at
> com.proj.core.backend.CoreBackendModule.configureServices(CoreBackendModule.java:98).
> >   at
> com.proj.core.domain.CoreDomainModule.configure(CoreDomainModule.java:47)
> >
> > 1 error
> >         at
> com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:358)
> >         at
> com.google.inject.internal.InjectorBuilder.initializeStatically(InjectorBuilder.java:153)
> >         at
> com.google.inject.internal.InjectorBuilder.build(InjectorBuilder.java:106)
> >         at com.google.inject.Guice.createInjector(Guice.java:93)
> >         at com.google.inject.Guice.createInjector(Guice.java:70)
> >         at
> com.proj.core.IntegrationTest.setupGuice(IntegrationTest.java:84)
> >         at
> com.proj.core.IntegrationTest.setupIntegrationTest(IntegrationTest.java:63)
> > ... Removed 22 stack frames
> >
> > Is it intended, that configuration failures don't break the tests? Btw.,
> > the test.using :fail_on_failure is left as default...
> >
> > Thanx && Cheers,
> > Martin
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message