From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18795 invoked by alias); 7 Mar 2012 11:58:22 -0000 Received: (qmail 18779 invoked by uid 22791); 7 Mar 2012 11:58:21 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_05,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 07 Mar 2012 11:58:09 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id B36C82F78009; Wed, 7 Mar 2012 11:58:07 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOLvQ7ltmVMH; Wed, 7 Mar 2012 11:58:06 +0000 (GMT) Message-ID: <4F574D4A.2090407@ecoscentric.com> Date: Wed, 07 Mar 2012 11:58:00 -0000 From: Alex Schuilenburg User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Ilija Kocho CC: eCos developers Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing References: <4F106345.4080902@siva.com.mk> <4F11574D.9070002@dallaway.org.uk> <4F11AC54.7000902@siva.com.mk> <4F1CB41C.90900@jifvik.org> <4F1DA9A0.5070702@siva.com.mk> <4F1FF5AD.4010901@ecoscentric.com> <4F39887A.5050905@siva.com.mk> <4F50F700.5080902@ecoscentric.com> <4F521D6A.4010500@siva.com.mk> <4F52B2C8.4010809@schuilenburg.org> <4F53C46B.4090502@dallaway.org.uk> <4F53FF0D.80107@ecoscentric.com> In-Reply-To: <4F53FF0D.80107@ecoscentric.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2012-03/txt/msg00017.txt.bz2 Hi Ilija, The RedBoot issue on the STM3210E-EVAL turned out to be a non-issue. eCos and eCosPro RedBoot are compatible. There was an eCosPro specific issue which I had forgotten about - sorry. The board ran overnight just over 1000 tests in different eCos configurations. There are currently 9 failures, listed according to their configuration name in our test farm. As jld knows, when a test fails in the farm it is automatically rerun an additional 2 times to confirm the failure is reproducible. All other tests in these configurations passed. ustl1: bvt05, bvt13, bvt17, sprintf2 infra1: except1, kexcept1, testintr absent1, compile1: testintr The eCos used was the version was dated 1 March and the configurations script segment to create each configuration is listed below. If you need any more info, just let me know. I unfortunately don't have the time at the moment to export the full set of results, but hopefully this will be enough for you to reproduce the failures. As a comparison, all tests passed in eCosPro for the STM3210E-EVAL with the obvious exception of the ustl1 configuration. ustl1: ecosconfig -i new stm3210e_eval cat > ustl1.ecm < infra1.ecm < absent1.ecm <