2009/6/26 Hannes Magnusson
> Hi all
>
> Is there *anyone* who needs anything to be able to debug bug reports,
> run sanitychecks, developing.. or whatever?
>
> We really need to improve our architecture/platform/os testing, even
> if its just "make all" compile checks.
> On php-webmaster@ we get
Hi Zoe and everyone :)
This thread is a proof that many people want to help the QA in PHP.
Although, many things done so far are redundant.
Specific valgrind reports per platform/architecture seems useless to me,
mainly because results are unreadable (most of the time the leak is in a
library tha
Hi Scott
From there it can run tests and do whatever we wish with the results,
like grab all test failures and upload it to your test result viewer.
If a build fails we can have it use twitter / irc to inform people
that a slave failed to build PHP for whatever reason.
I wonder if we can use
hi,
2009/6/27 Johannes Schlüter :
> Alright,
>
> I mentioned it in the last mails a bit in different ways so to make it
> clear:
>
> I'm aiming at re-tagging and packaging 5.3.0 to get these things in:
>
> - Andrei's calloc fix
> - Rasmus's/Ilia's curl fix
> - Improvements to the UPGRADING file
Alright,
I mentioned it in the last mails a bit in different ways so to make it
clear:
I'm aiming at re-tagging and packaging 5.3.0 to get these things in:
- Andrei's calloc fix
- Rasmus's/Ilia's curl fix
- Improvements to the UPGRADING file (everybody)
If possible (and I think it is) I'd
On Sat, 2009-06-27 at 01:37 +0200, Hannes Magnusson wrote:
> I haven't "wasted" time on finding out wtf these ini entries actually
> do, or even asked philip or gwynne to fix the inglés.. but if there is
> even a remote chance it'll make it into 5.3.0 I'll do whatever it
> takes to make it understa
On Fri, 2009-06-26 at 20:40 -0400, Ilia Alshanetsky wrote:
> After some conversations with Rasmus on IRC i've come up with the
> following patch:
>
> http://ilia.ws/patch/curl.txt
I this the latest patch and all agree t it? Or were there further
improvements?
Could somebody of you please commit
Hi,
On Fri, 2009-06-26 at 18:30 +0100, Scott MacVicar wrote:
> This freeze that you guys have implemented is frustrating, just branch
> 5_3 into a release branch and Johannes can take selective fixes from
> 5_3 as needed.
In my experience - from projects I participated as well were I just
obs
On Fri, 2009-06-26 at 14:23 -0700, Andrei Zmievski wrote:
> I found what is effectively a memory corruption bug in all the branches.
> pecalloc() uses
> the wrong length to zero out the memory. Patch is attached, although I'm
> somewhat
> concerned about using just (nmemb*len) instead of someth
