Return-Path: X-Original-To: apmail-stdcxx-dev-archive@www.apache.org Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B63B1D8CA for ; Tue, 4 Sep 2012 11:33:59 +0000 (UTC) Received: (qmail 18914 invoked by uid 500); 4 Sep 2012 11:33:59 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 18817 invoked by uid 500); 4 Sep 2012 11:33:58 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 18784 invoked by uid 99); 4 Sep 2012 11:33:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 11:33:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [64.34.174.152] (HELO hates.ms) (64.34.174.152) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 11:33:51 +0000 Received: from [192.168.72.105] (unknown [166.57.38.196]) by hates.ms (Postfix) with ESMTPSA id 1F5DB45C09A for ; Tue, 4 Sep 2012 11:33:30 +0000 (UTC) Message-ID: <5045E764.9090607@hates.ms> Date: Tue, 04 Sep 2012 07:35:00 -0400 From: Liviu Nicoara User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: dev@stdcxx.apache.org Subject: Re: STDCXX-1056 [was: Re: STDCXX forks] References: <40394653-8FCC-4D04-A108-2C650AF8F95B@hates.ms> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 09/04/12 05:37, Stefan Teleman wrote: > On Mon, Sep 3, 2012 at 11:57 PM, Stefan Teleman > wrote: > >> http://old.nabble.com/22.locale.numpunct.mt-run-hangs-td20133013.html > > Also see this thread: > > http://www.mail-archive.com/issues@stdcxx.apache.org/msg01182.html > > and this: > > https://issues.apache.org/jira/browse/STDCXX-839 Hi Stefan, IMHO Martin's report with the crashing test as well as your with the apparent hanging of the Intel build deserve more attention than other bug reports. A test timing out, regardless of the CPU activity, is more indicative of an inefficiency. All my tests were timing out Again, my concern is that a bug in the reference counting of std::string (or locale facets management) should be reproducible everywhere. If not, then only a subset of platforms are at fault -- so what is it? Is the atomic ops code defective there? We should be able to pinpoint the defect accurately. By no means I am dismissing it. It is at the very least an issue of efficiency. I will try an Intel C++ build on x86_64 at some point today. What build type was that? I also notice that you have 4.2.1 in your path? Are you building out of 4.2.1. tag? I built off 4.2.x branch which also has support for custom timeouts (--soft-timeout) in rw_test. Thanks! Liviu