Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> some test(s) hung on hadoop 2


Copy link to this message
-
Re: some test(s) hung on hadoop 2
Which branch/tag? Have you been able to reproduce this?
I tried on JDK7, Maven 3.0.5, on Fedora 19 x86_64, and could not reproduce.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Thu, Aug 15, 2013 at 12:54 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
> Hi,
> Some tests, e.g. FormatterCommandTest, hung when I ran test suite on hadoop
> 2 using Linux and JDK 7.
>
> Here is the command I used:
>
> ~/apache-maven-3.0.4/bin/mvn test -Dhadoop.profile=2.0
>
> Here is related portion from jstack:
>
> Thread 1895: (state = IN_NATIVE)
>  - java.io.FileInputStream.readBytes(byte[], int, int) @bci=0 (Interpreted
> frame)
>  - java.io.FileInputStream.read(byte[], int, int) @bci=4, line=242
> (Interpreted frame)
>  - java.io.BufferedInputStream.fill() @bci=175, line=235 (Interpreted frame)
>  - java.io.BufferedInputStream.read() @bci=12, line=254 (Interpreted frame)
>  - jline.internal.TerminalLineSettings.exec(java.lang.String[]) @bci=54,
> line=191 (Interpreted frame)
>  - jline.internal.TerminalLineSettings.exec(java.lang.String) @bci=26,
> line=173 (Interpreted frame)
>  - jline.internal.TerminalLineSettings.stty(java.lang.String) @bci=26,
> line=168 (Interpreted frame)
>  - jline.internal.TerminalLineSettings.set(java.lang.String) @bci=2,
> line=76 (Interpreted frame)
>  - jline.UnixTerminal.init() @bci=15, line=54 (Interpreted frame)
>  - jline.TerminalFactory.create() @bci=298, line=101 (Interpreted frame)
>  - jline.TerminalFactory.get() @bci=14, line=159 (Interpreted frame)
>  - jline.console.ConsoleReader.<init>(java.lang.String,
> java.io.InputStream, java.io.OutputStream, jline.Terminal,
> java.lang.String) @bci=217, line=227 (Interpreted frame)
>  - jline.console.ConsoleReader.<init>(java.lang.String,
> java.io.InputStream, java.io.OutputStream, jline.Terminal) @bci=7, line=219
> (Interpreted frame)
>  - jline.console.ConsoleReader.<init>() @bci=16, line=207 (Interpreted
> frame)
>  - org.apache.accumulo.core.util.shell.Shell.<init>() @bci=5, line=207
> (Interpreted frame)
>  -
> org.apache.accumulo.core.client.mock.MockShell.<init>(java.io.InputStream,
> java.io.OutputStream) @bci=1, line=39 (Interpreted frame)
>  - org.apache.accumulo.core.util.shell.command.FormatterCommandTest.test()
> @bci=78, line=57 (Interpreted frame)
>  - sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method,
> java.lang.Object, java.lang.Object[]) @bci=0 (Interpreted frame)
>  - sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) @bci=87, line=57 (Interpreted frame)
>  - sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object,
> java.lang.Object[]) @bci=6, line=43 (Interpreted frame)
>  - java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object[])
> @bci=57, line=606 (Interpreted frame)
>  - org.junit.runners.model.FrameworkMethod$1.runReflectiveCall() @bci=15,
> line=47 (Interpreted frame)
>  - org.junit.internal.runners.model.ReflectiveCallable.run() @bci=1,
> line=12 (Interpreted frame)
>  -
> org.junit.runners.model.FrameworkMethod.invokeExplosively(java.lang.Object,
> java.lang.Object[]) @bci=10, line=44 (Interpreted frame)
>  - org.junit.internal.runners.statements.InvokeMethod.evaluate() @bci=12,
> line=17 (Interpreted frame)
>  -
> org.junit.runners.ParentRunner.runLeaf(org.junit.runners.model.Statement,
> org.junit.runner.Description, org.junit.runner.notification.RunNotifier)
> @bci=17, line=271 (Interpreted frame)
>
> Did anyone see similar issue ?
>
> Thanks