Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 45839 invoked from network); 23 Mar 2007 17:50:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Mar 2007 17:50:27 -0000 Received: (qmail 79787 invoked by uid 500); 23 Mar 2007 17:50:35 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 79765 invoked by uid 500); 23 Mar 2007 17:50:35 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 79748 invoked by uid 99); 23 Mar 2007 17:50:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Mar 2007 10:50:35 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Mar 2007 10:50:24 -0700 Received: from [10.70.3.116] ([10.70.3.116]) by moroha.quovadx.com (8.13.6/8.13.6) with ESMTP id l2NHo0fb026313 for ; Fri, 23 Mar 2007 17:50:00 GMT Message-ID: <46041303.6040209@roguewave.com> Date: Fri, 23 Mar 2007 11:48:51 -0600 From: Andrew Black User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: legacy tests on Windows References: <4603FBC8.6040804@roguewave.com> In-Reply-To: <4603FBC8.6040804@roguewave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Greetings Martin. I think it's likely that we will need to make some changes to the windows infrastructure. The cause of the missing legacy tests is twofold. First, the legacy test executables appear to fail to compile in dynamic builds because the legacy test driver symbols aren't resolved. This seems to point to a failure to export them correctly. Second, the runall.wsf script doesn't pass the names of non-existent executables to the exec script. Therefore, you don't see any targets in the COMPILE or LINK states when the exec utility runs. Looking at the runall.wsf and generated .stdcxx_runtests solution, I believe that the cause of the format messages likely is coming from a failure to pass the compatibility mode options to the test suite. Farid, the additional switches that need to be passed to the exec utility when running the tests are '--compat -x "--compat -O -"' (minus the single quotes). Hopefully the shell will handle the quote processing correctly. --Andrew Black Martin Sebor wrote: > I noticed that the legacy tests (like 21_native.exe) are reported > with the status of FORMAT in some of our most recent results (from > this morning) and missing from others. > > Andrew, do you have any idea what's going on here? Do we still need > to change the Windows test harness to enable the legacy output mode > in the driver? What about the builds where they are missing? > > Legacy tests with FORMAT status: > http://people.apache.org/~sebor/stdcxx/results/windows-vista-amd64-msvc-64b-8.0-15s-log.gz.txt > > > Missing legacy tests: > http://people.apache.org/~sebor/stdcxx/results/windows-vista-amd64-msvc-64b-8.0-12d-log.gz.txt > > > Thanks > Martin