From dev-return-25717-apmail-harmony-dev-archive=harmony.apache.org@harmony.apache.org Fri Apr 06 03:00:22 2007 Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 37961 invoked from network); 6 Apr 2007 03:00:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Apr 2007 03:00:21 -0000 Received: (qmail 80235 invoked by uid 500); 6 Apr 2007 03:00:25 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 80208 invoked by uid 500); 6 Apr 2007 03:00:25 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 80199 invoked by uid 99); 6 Apr 2007 03:00:25 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 20:00:25 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ivavladimir@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 20:00:17 -0700 Received: by ug-out-1314.google.com with SMTP id z36so1022905uge for ; Thu, 05 Apr 2007 19:59:56 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GOO2epOXTIsopvviny+qk02TvMJMl0Z+KLNlWgDhrZ/RyGJreZRxhf7vjE4o0ZH+3vs0h2tMvzhHNGUnFQACtWzTkZNK49lHjhZpJRNNbFzpJByKf91VEY9LEovVb1aVO9g88aCzNI91Bo4InlvTFtPOKUs7qAzSLM/NMuZn04U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tmP4ixpFpysvowYY/785c5l+3ZZWVTEsFUv9x2lRV5aCJGBWuLXCRJfElzoa40H53LM/+pGHZ6jvp/EHgsABM6Xpe4wWhhph8bpMuM0mjh0uk3yBQq5QL5oyiMUGXibBsI53/s86u0eoe1MGJsfg6c9HB+vCT7wZZfaY/78jnVw= Received: by 10.78.139.1 with SMTP id m1mr456142hud.1175828395981; Thu, 05 Apr 2007 19:59:55 -0700 (PDT) Received: by 10.78.200.14 with HTTP; Thu, 5 Apr 2007 19:59:55 -0700 (PDT) Message-ID: <7273946b0704051959g1445fde5qdf0f062c805ae2e0@mail.gmail.com> Date: Fri, 6 Apr 2007 09:59:55 +0700 From: "Vladimir Ivanov" To: dev@harmony.apache.org Subject: Re: [drlvm][threading] Some smoke tests started to hang this week on linux x86 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7273946b0703281939j60a55c57tb3fe356246a52392@mail.gmail.com> <7273946b0704040351n73e7c78cr11d7418a7c5f7a9c@mail.gmail.com> <7273946b0704050547n4df007ek50f5cd0e6d0a665d@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 4/5/07, Alexey Varlamov wrote: > 2007/4/5, Vladimir Ivanov : > > OK, today I run smoke test gc.SynchronizedFinilazersTest on SUSE 9 > > Linux x86_64 in cycle. > > I found: > > - on current DRLVM this test hang on 13 iteration; > > - on r522000 test passed for 100 iteration; > > - on r522100 test hang on 53 iteration. > > > > The differences between 522100 and 522000 are: > > U vm/include/open/hythread_ext.h > > U vm/interpreter/src/interpreter.cpp > > U vm/thread/src/thread_java_monitors.c > > U vm/thread/src/hythr.exp > > U vm/thread/src/hythr.def > > U vm/thread/src/thread_native_fat_monitor.c > > U vm/thread/src/thread_native_basic.c > > U vm/thread/src/thread_ti_monitors.c > > U vm/thread/src/thread_native_tls.c > > U vm/thread/src/thread_private.h > > U vm/thread/src/thread_java_basic.c > > U vm/thread/src/thread_native_suspend.c > > U vm/thread/src/thread_init.c > > U vm/vmcore/src/thread/thread_manager.cpp > > U vm/vmcore/src/jvmti/jvmti_pop_frame.cpp > > U vm/vmcore/src/jvmti/jvmti_step.cpp > > U vm/vmcore/src/jvmti/jvmti_break.cpp > > U vm/jitrino/src/jet/compiler.cpp > > U vm/jitrino/src/vm/drl/DrlVMInterface.cpp > > > > Now I run this test on r522000 for 3000 iteration (400 already > > passed). If it passed I'll try to narrow the guilty changes. > The test passed on r522000 for 3000 iteration. > AFAIS in this interval was the sole drlvm commit: > [r522033] H3413, refactor, cleanup of exception safepoint callback build. Thanks. The result is: - the test is hang on the r522033 (iteration 143) - the test is passed already for 670 iteration on r522032. Could somebody from our thread guru evaluate it? thanks, Vladimir > > > > > thanks, Vladimir > > > > > > On 4/4/07, Vladimir Ivanov wrote: > > > The test gc.SynchronizedFinilazersTest still hangs up on SUSE 9 Linux x86_64. > > > OK, I'll exclude it locally. > > > > > > thanks, Vladimir > > > > > > > > > On 3/30/07, Pavel Rebriy wrote: > > > > I had a similar problem with WinX64 (see "[drlvm][stability][winx64] > > > > finalization tests irregular failure" branch for details). > > > > I had a problem with HARMONY-3485 commit. I rolled back it, and it was > > > > successful for tests passing :) > > > > I could solve the problem with smoke tests. > > > > > > > > On 30/03/07, Elena Semukhina wrote: > > > > > > > > > > On 3/29/07, Peter Novodvorsky wrote: > > > > > > > > > > > > HARMONY-3495 shows that gc.NPE fails in the JVM shutdown stage. Do you > > > > > > think that all other tests fail in the same situation? Can you > > > > > > explain, what makes you think that all these tests fail for the same > > > > > > reason? > > > > > > > > > > > > > > > It looks like the gc.PhantomReferenceQueueTest hangs at the shutdown stage > > > > > as well: it prints PASSED and then hangs with the same stack traces. > > > > > gc.SynchronizedFinilazersTest ( > > > > > https://issues.apache.org/jira/browse/HARMONY-3517) shows up another stack > > > > > traces. > > > > > > > > > > I'm not sure that the cause is the same for both issues. I'm only almost > > > > > sure that we have these troubles since last weekend. > > > > > > > > > > Thanks, > > > > > Elena > > > > > > > > > > Thanks, > > > > > > Peter. > > > > > > > > > > > > > > > > > > On 3/29/07, Elena Semukhina wrote: > > > > > > > I managed to reproduce gc.PhantomReferenceQueueTest hang on SUSE 9 > > > > > Linux > > > > > > > x86_64 as well. > > > > > > > > > > > > > > It seems that we have new serious problem in threading system since > > > > > last > > > > > > > weekend. A number of test can hang intermittently. Each day we see new > > > > > > > test's hang. > > > > > > > > > > > > > > Shouldn't we focus efforts on investigating this issue? From my > > > > > > experiens > > > > > > > gc.NPE hangs more often than others and could be a good candidate for > > > > > > issue > > > > > > > reproducing (https://issues.apache.org/jira/browse/HARMONY-3495) > > > > > > > > > > > > > > Elena > > > > > > > > > > > > > > On 3/29/07, Vladimir Ivanov wrote: > > > > > > > > > > > > > > > > Actually not Linux x86 only :( The test gc.NPE hangs on Linux x86_64 > > > > > > also. > > > > > > > > Today the test gc.PhantomReferenceQueueTest hangs on SUSE 9 Linux > > > > > > x86_64. > > > > > > > > Note, all these hangs are intermittent. > > > > > > > > > > > > > > > > Thanks, Vladimir > > > > > > > > > > > > > > > > > > > > > > > > On 3/28/07, Elena Semukhina wrote: > > > > > > > > > This week I noticed that some smoke tests hung in iterative runs > > > > > on > > > > > > > > linux > > > > > > > > > x86. I did not see this before. Possibly they detect some new > > > > > > issues. > > > > > > > > > > > > > > > > > > Yesterday I filed > > > > > > https://issues.apache.org/jira/browse/HARMONY-3495about > > > > > > > > > gc.NPE because CC also detected the hang. We excluded gc.NPE. > > > > > > > > > > > > > > > > > > Today I saw that gc.SynchronizedFinilazersTest hung and filed > > > > > > > > > https://issues.apache.org/jira/browse/HARMONY-3517. > > > > > > > > > > > > > > > > > > I wouldn't like to exclude each test which hangs for now. Possibly > > > > > > we > > > > > > > > can > > > > > > > > > fix the issue quickly. > > > > > > > > > > > > > > > > > > I managed to reproduce gc.SynchronizedFinilazersTest hang after > > > > > 450 > > > > > > runs > > > > > > > > in > > > > > > > > > JET and after 50 runs in OPT. I provided te stack traces in JIRAs. > > > > > > > > Possibly > > > > > > > > > they could be useful. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Thanks, > > > > > > > > > Elena > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Thanks, > > > > > > > Elena > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Thanks, > > > > > Elena > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > > > Pavel Rebriy > > > > > > > > > >