Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <31734949.1169206469956.JavaMail.jira@brutus>
Date: Fri, 19 Jan 2007 03:34:29 -0800 (PST)
From: "Evgueni Brevnov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-3018) [drlvm][thread manager][unit]
 cunit test thread/test_ti_instrum.c fails from time to time
In-Reply-To: <197808.1169107769997.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466030 ] 

Evgueni Brevnov commented on HARMONY-3018:
------------------------------------------

Elena,

Mostlikely, this is a test problem....need test investigation

Evgueni

> [drlvm][thread manager][unit] cunit test thread/test_ti_instrum.c fails from time to time
> -----------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3018
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3018
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Elena Semukhina
>
> I managed to reproduce the failure with iterative runs on linux ia32 gcc release build:
> test test_ti_instrum failed:
> test_jthread_get_blocked_count start
>      [echo] ERROR: Test failed: Wrong number waiting on monitor threads (/export/lab_drlbuild/combined_gcc/CVS_20070117_0002_H/drlvm/trunk/vm/tests/unit/thread/test_ti_instrum.c:139)
> To run the test iteratively please use the following command:
>  i=0; while true; do ./test_ti_instrum -Dorg.apache.harmony.vm.vmdir=$DRLVM_HOME/bin/default -Djava.home=$DRLVM_HOME; ec=$?; echo $i $ec; test $ec != 0 && break; i=$[i+1]; done
> Once I saw the failure on linux ia32 icc debug build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira