Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:29442
Return-Path: <helly@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 63707 invoked by uid 1010); 15 May 2007 16:07:14 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 63692 invoked from network); 15 May 2007 16:07:14 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 May 2007 16:07:14 -0000
Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain php.net from 85.214.94.56 cause and error)
X-PHP-List-Original-Sender: helly@php.net
X-Host-Fingerprint: 85.214.94.56 aixcept.net  
Received: from [85.214.94.56] ([85.214.94.56:50830] helo=h1149922.serverkompetenz.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 93/C2-39652-1BAD9464 for <internals@lists.php.net>; Tue, 15 May 2007 12:07:13 -0400
Received: from localhost (h1149922.serverkompetenz.net [85.214.94.56])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by h1149922.serverkompetenz.net (Postfix) with ESMTP id 671C61B3606;
	Tue, 15 May 2007 18:07:09 +0200 (CEST)
Date: Tue, 15 May 2007 18:07:11 +0200
Reply-To: Marcus Boerger <helly@php.net>
X-Priority: 3 (Normal)
Message-ID: <835117378.20070515180711@marcus-boerger.de>
To: Zoe Slattery <zoe.slattery@googlemail.com>
CC: internals@lists.php.net, Marcus Boerger <helly@php.net>, 
	Antony Dovgal <antony@zend.com>, <kraghuba@in.ibm.com>
In-Reply-To: <4649D4F0.1010202@googlemail.com>
References: <4649D4F0.1010202@googlemail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Committing failing tests?
From: helly@php.net (Marcus Boerger)

Hello Zoe,

  I did the same with a certain case in SPL. The result was that any
test run of 5.2.1 had failures on that test while as HEAD did not have
it anymore. The thing is that I used it to remind myself that i have
to merge the fix and to anybody else that this is not working correct
yet. In this case however you need to keep track of changes in the area
because sometimes the actual fix chnages the resulting output a bit from
the original expectation. So you should stay in touch with the actual
developer, of course at least informing him of the error.

best regards
marcus

Tuesday, May 15, 2007, 5:42:40 PM, you wrote:

> Hi

> I have some updates that I'd like to make to 
> ext/tests/standard/array/range.phpt, the updates work fine with 
> unicode.semantics=off but not with unicode.semantics=on. The problem 
> seems to be that the warning Notices that are generated are different 
> with unicode on. This doesn't look like intentional behaviour but I'm 
> guessing it might well be something that isn't implemented yet.

> So, my question is - is it reasonable/helpful to add a test in CVS that 
> I know will fail if it's in an area that is currently under development?

> Zoe Slattery
> IBM UK



Best regards,
 Marcus