I haven't seen this before. I always run clean build & tests at cli before submitting.
On Mon, Jul 7, 2014 at 10:30 PM, Timothy Chen <[email protected]> wrote: > Hi folks, > > I grabbed latest master and getting tests failed a bit randomly, all > about metrics exception. One example: > > java.lang.IllegalArgumentException: A metric named > drill.exec.work.running_fragments.31014 already exists > at > com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:91) > at > org.apache.drill.exec.work.WorkManager.start(WorkManager.java:100) > at org.apache.drill.exec.server.Drillbit.run(Drillbit.java:150) > at > org.apache.drill.BaseTestQuery.openClient(BaseTestQuery.java:100) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:606) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at > org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > > Seems like we're doing port hunting on tests startup for drillbits as > before, but not sure if we used to register metrics in the past. I > haven't dug deep yet, but anyone seen this issue? > > Tim >
