I had copied the wrong text into the bug. I fixed that. On Mon, Jan 22, 2018 at 10:22 AM, Casey Stella <ceste...@gmail.com> wrote:
> This could be one of those intermittent test failures related to timing. > Specifically this: > > test(org.apache.metron.rest.controller.SensorIndexingConfigController > IntegrationTest) > Time elapsed: 0.064 sec <<< FAILURE! > java.lang.AssertionError: Status expected:<404> but was:<200> > at org.springframework.test.util.AssertionErrors.fail( > AssertionErrors.java:54) > at org.springframework.test.util.AssertionErrors.assertEquals( > AssertionErrors.java:81) > at org.springframework.test.web.servlet.result. > StatusResultMatchers$10.match(StatusResultMatchers.java:664) > at org.springframework.test.web.servlet.MockMvc$1.andExpect( > MockMvc.java:171) > at org.apache.metron.rest.controller. > SensorIndexingConfigControllerIntegrationTest.test( > SensorIndexingConfigControllerIntegrationTest.java:146) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall( > FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run( > ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively( > FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod. > evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores. > evaluate(RunBefores.java:26) > at org.springframework.test.context.junit4.statements. > RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks. > java:75) > at org.springframework.test.context.junit4.statements. > RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86) > at org.springframework.test.context.junit4.statements. > SpringRepeat.evaluate(SpringRepeat.java:84) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.springframework.test.context.junit4. > SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252) > at org.springframework.test.context.junit4. > SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren( > ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate( > ParentRunner.java:229) > at org.springframework.test.context.junit4.statements. > RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) > at org.springframework.test.context.junit4.statements. > RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.springframework.test.context.junit4. > SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute( > JUnit4Provider.java:283) > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeWithRerun(JUnit4Provider.java:173) > at org.apache.maven.surefire.junit4.JUnit4Provider. > executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke( > JUnit4Provider.java:128) > at org.apache.maven.surefire.booter.ForkedBooter. > invokeProviderInSameClassLoader(ForkedBooter.java:203) > at org.apache.maven.surefire.booter.ForkedBooter. > runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main( > ForkedBooter.java:103) > > > > On Mon, Jan 22, 2018 at 10:21 AM, Nick Allen <n...@nickallen.org> wrote: > > > I had created this JIRA for the specific issue earlier this morning. I > > have no idea why it is breaking and I am not currently looking into it. > > Definitely nothing to do with the most recent commit. > > > > https://issues.apache.org/jira/browse/METRON-1414 > > > > > > On Mon, Jan 22, 2018 at 10:18 AM, Otto Fowler <ottobackwa...@gmail.com> > > wrote: > > > > > https://travis-ci.org/apache/metron/builds/330900667 > > > > > >
