Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of mark.g.brown@gmail.com
 designates 64.233.178.250 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=dqfiF0GK9XrXIonVS++IeTftQMYRUZKNTq2QVb9yv+VKkp+eHrQFMZ8KMXQfCigGb8GExZ+pYZaWY7vhTiAPW14IDDXv8DTXfBejZEI8K/Nm07FFls/7AIeqj7nX4wQdO0ynQbvw5tENJr5wCjeQ001CwwwNMN2M7AGJ7Jmucyw=
Message-ID: <2494433f0801021503t5eb12d29pd23f96e144513d36@mail.gmail.com>
Date: Wed, 2 Jan 2008 16:03:16 -0700
From: "Mark Brown" <mark.g.brown@gmail.com>
To: stdcxx-dev@incubator.apache.org
Subject: Re: prototype of the "expected failures" enhancement (STDCXX-683)
In-Reply-To: <477999B0.8010409@roguewave.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <477999B0.8010409@roguewave.com>

Martin,

Most of the links to the log files are broken. They all point to files
in http://people.apache.org/tmp/. Also, I'm not sure I understand how
rows in the tables are supposed to be arranged now. If I recall, they
used to be ordered alphabetically but after your change 26 comes
before 23, and 23 before 27. Is that intended?

2  	26.class.gslice  	46230  	162
5 	23.deque.special 	61465 	1536
7 	27_basic_ios 	0 	1

-- Mark

On Dec 31, 2007 6:38 PM, Martin Sebor <sebor@roguewave.com> wrote:
> The commit below implements an initial prototype of the "expected
> failures" enhancement described in STDCXX-683. The prototype can
> be viewed on the usual test result page:
>    http://people.apache.org/~sebor/stdcxx/results/builds
>
> http://svn.apache.org/viewvc?rev=607788&view=rev
>
> The new file, etc/config/xfail.txt, is intended to contain a list
> of known failures in the test suite (including examples and locales).
> The comments in the file explain how to make a failure in a component
> as expected.
>
> Let me know what you all think: questions, suggestions for changes,
> or bug reports are all welcome!
>
> Happy new year!
> Martin
>
> PS I've tested the changes with build logs on most platforms but I
> forgot to include Windows. As usual, things are different there and
> the results aren't quite satisfactory. I'll work on fixing those as
> soon as I get a chance.
>