On Thu, Oct 8, 2009 at 4:21 PM, ant elder <[email protected]> wrote: > On Thu, Oct 8, 2009 at 4:02 PM, Luciano Resende <[email protected]> wrote: >> On Thu, Oct 8, 2009 at 2:21 AM, ant elder <[email protected]> wrote: >>> I'm also getting a test fail in binding-atom-runtime: >>> >>> <failure message="expected:<304> but was:<200>" >>> type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: >>> expected:<304> but was:<200> >>> at junit.framework.Assert.fail(Assert.java:47) >>> at junit.framework.Assert.failNotEquals(Assert.java:277) >>> at junit.framework.Assert.assertEquals(Assert.java:64) >>> at junit.framework.Assert.assertEquals(Assert.java:195) >>> at junit.framework.Assert.assertEquals(Assert.java:201) >>> at >>> org.apache.tuscany.sca.binding.atom.ProviderFeedEntityTagsTestCase.testUnmodifiedGetIfUnModified(ProviderFeedEntityTagsTestCase.java:192) >>> >>> ...ant >>> >> >> I can't reproduce it locally and I get a full clean build from >> modules, can you give more info about your environment ? >> > > Maven 2.1.0, Sun Java 1.6.0_13-b03, WinXP. > > It looks like its intermittent as it works now but didn't repeatedly > earlier. Do the tests require remote network access? My network is a > bit intermittent right now so if so that could be it I suppose though > the test fail is saying it got an http 200 return code so that doesn't > seem like a network problem. > > ...ant >
This is still happening and its not just me it happens on the Hudson build too so I've taken out the test for now and raised TUSCANY-3299. Ideally the build wouldn't have tests that require remote internet resources as they're always going to be a little flaky, at least those types of tests should be itests as with they way we have the build when module tests fail it also fails the distribution build which then fails all the itests that validate the distribution, which means you can't use mvn -fae or -fn to get passed the build test failure. ...ant
