Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id ED769200B53 for ; Tue, 12 Jul 2016 11:02:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EBFF7160A56; Tue, 12 Jul 2016 09:02:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 44123160A75 for ; Tue, 12 Jul 2016 11:02:23 +0200 (CEST) Received: (qmail 61500 invoked by uid 500); 12 Jul 2016 09:02:21 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 61265 invoked by uid 99); 12 Jul 2016 09:02:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jul 2016 09:02:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E1DA22C02AC for ; Tue, 12 Jul 2016 09:02:20 +0000 (UTC) Date: Tue, 12 Jul 2016 09:02:20 +0000 (UTC) From: "Dmitri Blinov (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (JEXL-206) testCancelLoopWait() test hangs sporadically? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 12 Jul 2016 09:02:24 -0000 Dmitri Blinov created JEXL-206: ---------------------------------- Summary: testCancelLoopWait() test hangs sporadically? Key: JEXL-206 URL: https://issues.apache.org/jira/browse/JEXL-206 Project: Commons JEXL Issue Type: Bug Affects Versions: 3.0 Reporter: Dmitri Blinov I'm struggling with strange behaviour of the building process, it seems that time after time the process hangs somewhere in the middle of the tests stage. First I thought it was somehow related to memory problems so I changed fork mode of the test plugin by adding pertest to maven-surefire-plugin configuration. But that helped for a couple of times to cleanly build jexl and run all tests successfully. The other times it simply hanged on test stage. I have managed to detect that it is the testCancelLoopWait() test that hangs. It writes to the console the message {panel} WARNING: org.apache.commons.jexl3.ScriptCallableTest.testCancelLoopWait@1:20 execution cancelled {panel} and hangs with its stack trace as follows: {code} org.apache.commons.jexl3.internal.Interpreter.visit(Interpreter.java:893) org.apache.commons.jexl3.parser.ASTWhileStatement.jjtAccept(ASTWhileStatement.java:18) org.apache.commons.jexl3.internal.Interpreter.visit(Interpreter.java:1119) org.apache.commons.jexl3.parser.ASTJexlScript.jjtAccept(ASTJexlScript.java:55) org.apache.commons.jexl3.internal.Interpreter.interpret(Interpreter.java:210) org.apache.commons.jexl3.internal.Script$Callable.interpret(Script.java:364) org.apache.commons.jexl3.internal.Script$Callable.call(Script.java:372) - locked org.apache.commons.jexl3.internal.Script$Callable@18399f62 java.util.concurrent.FutureTask.run(FutureTask.java:262) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) {code} The problem started manifesting itself right after I had added ScriptInterruptableTest.java (see JEXL-204) but as I understand this test script is completely unrelated to ScriptCallableTest.java so I think it's merely a conicidence. I could not write anything in ScriptInterruptableTest and screw up ScriptCallableTest, right? PS. I have managed to catch this exactly behavior after removing ScriptInterruptableTest.java completely and making clean build, so I'm 100% sure there is something wrong with the original code, may be race condition or something. -- This message was sent by Atlassian JIRA (v6.3.4#6332)