On Fri, Dec 2, 2011 at 4:47 PM, Matteo Beccati wrote:
> Hi,
>
> On 26/11/2011 01:05, Ferenc Kovacs wrote:
> > FreeBSD:
> >
> > As I mentioned previously, the IO perf is really bad for those two vm's,
> so
> > if we can't find a solution, or other place to run those, I will have to
> > turn those
Hi,
On 26/11/2011 01:05, Ferenc Kovacs wrote:
> FreeBSD:
>
> As I mentioned previously, the IO perf is really bad for those two vm's, so
> if we can't find a solution, or other place to run those, I will have to
> turn those off, as they really slows down the build(they are like 5-10
> times slow
Hi,
Recent activity:
Alexey Shein dug through the failing symfony2 tests, and it turned out that
3 tests were bugged, he went ahead and fixed it (
https://github.com/symfony/symfony/pull/2750), one from the other two is a
sporadic test, it can fail randomly, the last one fails in our specific
set
Yesterday we were talking about enabling more extensions and adding pecl
> into the mix:
> http://www.mail-archive.com/internals@lists.php.net/msg54220.html
> I think it would be a good idea to try to fix the currently failing tests.
> http://ci.qa.php.net/job/php-src-5.3-matrix-tests/35/testReport
On Tue, Nov 8, 2011 at 11:36 AM, Dirk Haun wrote:
> Quoting Ferenc Kovacs :
>
> There is only three failing tests left on the debian slaves:
>>
>> For 5.3
>> ext/phar/tests/phar_oo_005.**phpt.Phar and RecursiveDirectoryIterator
>> 0.01 20
>> ext/spl/tests/bug60082.phpt.**Bug #60082 (100% CPU / w
Quoting Ferenc Kovacs :
There is only three failing tests left on the debian slaves:
For 5.3
ext/phar/tests/phar_oo_005.phpt.Phar and RecursiveDirectoryIterator 0.01 20
ext/spl/tests/bug60082.phpt.Bug #60082 (100% CPU / when using references
with ArrayObject(&$ref))
FWIW, the test for Bug #60
On Mon, Nov 7, 2011 at 4:42 PM, Ferenc Kovacs wrote:
>
>
> On Mon, Nov 7, 2011 at 11:14 AM, Ferenc Kovacs wrote:
>
>>
>>
>> On Thu, Nov 3, 2011 at 8:15 PM, Ferenc Kovacs wrote:
>>
>>>
>>>
>>> On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr wrote:
>>>
Hi Ferenc:
On 03 Nov 2011, at 19
On Mon, Nov 7, 2011 at 11:14 AM, Ferenc Kovacs wrote:
>
>
> On Thu, Nov 3, 2011 at 8:15 PM, Ferenc Kovacs wrote:
>
>>
>>
>> On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr wrote:
>>
>>> Hi Ferenc:
>>>
>>> On 03 Nov 2011, at 19:01, Ferenc Kovacs wrote:
>>>
>>> > Of course there are ways to improve t
On Thu, Nov 3, 2011 at 8:15 PM, Ferenc Kovacs wrote:
>
>
> On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr wrote:
>
>> Hi Ferenc:
>>
>> On 03 Nov 2011, at 19:01, Ferenc Kovacs wrote:
>>
>> > Of course there are ways to improve the current setup, I listed those
>> ideas
>> > at https://wiki.php.net/r
On Sat, Nov 5, 2011 at 4:23 PM, Hannes Magnusson wrote:
> On Sat, Nov 5, 2011 at 10:42, Ferenc Kovacs wrote:
>
> > I just noticed that the mail will be sent on each configuration build
> > (debian 32bit, debian 64bit, freebsd 32bit, freebsd 64bit), which is of
> > course a little bit too much, I
On Sat, Nov 5, 2011 at 10:42, Ferenc Kovacs wrote:
> I just noticed that the mail will be sent on each configuration build
> (debian 32bit, debian 64bit, freebsd 32bit, freebsd 64bit), which is of
> course a little bit too much, I'm looking into resolving this, so to only
> send email on the pare
On Sat, Nov 5, 2011 at 10:42 AM, Ferenc Kovacs wrote:
>
>
> On Fri, Nov 4, 2011 at 2:00 AM, Ferenc Kovacs wrote:
>
>>
>>
>> On Fri, Nov 4, 2011 at 12:21 AM, Ferenc Kovacs wrote:
>>
>>>
>>>
>>> On Fri, Nov 4, 2011 at 12:20 AM, Stefan Marr wrote:
>>>
Hi:
On 04 Nov 2011, at 00:12,
On Fri, Nov 4, 2011 at 2:00 AM, Ferenc Kovacs wrote:
>
>
> On Fri, Nov 4, 2011 at 12:21 AM, Ferenc Kovacs wrote:
>
>>
>>
>> On Fri, Nov 4, 2011 at 12:20 AM, Stefan Marr wrote:
>>
>>> Hi:
>>>
>>> On 04 Nov 2011, at 00:12, Ferenc Kovacs wrote:
>>>
>>> > I almost forget to mention, but the email n
On Fri, Nov 4, 2011 at 12:21 AM, Ferenc Kovacs wrote:
>
>
> On Fri, Nov 4, 2011 at 12:20 AM, Stefan Marr wrote:
>
>> Hi:
>>
>> On 04 Nov 2011, at 00:12, Ferenc Kovacs wrote:
>>
>> > I almost forget to mention, but the email notification also supports
>> defining different recipients for each eve
On Fri, Nov 4, 2011 at 12:20 AM, Stefan Marr wrote:
> Hi:
>
> On 04 Nov 2011, at 00:12, Ferenc Kovacs wrote:
>
> > I almost forget to mention, but the email notification also supports
> defining different recipients for each event, so for example the commiters
> could still get the notification f
Hi:
On 04 Nov 2011, at 00:12, Ferenc Kovacs wrote:
> I almost forget to mention, but the email notification also supports defining
> different recipients for each event, so for example the commiters could still
> get the notification for each of their commits/builds until the build is back
> t
On Thu, Nov 3, 2011 at 11:58 PM, Rasmus Lerdorf wrote:
> On 11/03/2011 03:47 PM, Ferenc Kovacs wrote:
> > A, it will report every test failure, but we fix all of our tests so we
> > are cool. (my preference)
>
> But even if we do that, when a test does fail, it may take a couple of
> days to fix
On 11/03/2011 03:47 PM, Ferenc Kovacs wrote:
> A, it will report every test failure, but we fix all of our tests so we
> are cool. (my preference)
But even if we do that, when a test does fail, it may take a couple of
days to fix it. It would be nice if we didn't get an internals email for
every c
On Thu, Nov 3, 2011 at 11:33 PM, Rasmus Lerdorf wrote:
> On 11/03/2011 02:26 PM, Ferenc Kovacs wrote:
> > We could set up the email notification any time, we would just have to
> > agree where to send (internals, php-qa, creating a dedicated mailing
> list?)
> > and when to send (as I added to th
On 11/03/2011 02:26 PM, Ferenc Kovacs wrote:
> We could set up the email notification any time, we would just have to
> agree where to send (internals, php-qa, creating a dedicated mailing list?)
> and when to send (as I added to the RFC, having failing tests can be a
> problem from the notificatio
On Thu, Nov 3, 2011 at 10:25 PM, Klaus Silveira
wrote:
> Yes, it's a wonderful setup. Great work, Ferenc! :D
>
> This does give a nice motivation to write more tests and increase the code
> coverage, doesn't it?
>
Yes, and first of all, to fix the currently failing tests.
We also had a discussion
On Thu, Nov 3, 2011 at 10:22 PM, Felipe Pena wrote:
> 2011/11/3 Ferenc Kovacs :
> > On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira <
> cont...@klaussilveira.com>wrote:
> >
> >> That's kind of a general setup, Stefan. Sending an email to the commiter
> >> that broke the build with details of the b
Yes, it's a wonderful setup. Great work, Ferenc! :D
This does give a nice motivation to write more tests and increase the code
coverage, doesn't it?
On Thu, Nov 3, 2011 at 7:22 PM, Felipe Pena wrote:
> 2011/11/3 Ferenc Kovacs :
> > On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira <
> cont...@klau
2011/11/3 Ferenc Kovacs :
> On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira
> wrote:
>
>> That's kind of a general setup, Stefan. Sending an email to the commiter
>> that broke the build with details of the build process, as well sending an
>> email to a mailing list.
>>
>> I'll be looking into thi
On Thu, Nov 3, 2011 at 8:41 PM, Klaus Silveira wrote:
> That's kind of a general setup, Stefan. Sending an email to the commiter
> that broke the build with details of the build process, as well sending an
> email to a mailing list.
>
> I'll be looking into this Jenkins issue (JENKINS-5931). Maybe
On Thu, Nov 3, 2011 at 8:33 PM, Stefan Marr wrote:
> Hi:
>
> On 03 Nov 2011, at 20:15, Ferenc Kovacs wrote:
>
> > The usual setup is that you have a mailing list/alias which always gets
> a mail about the build results (which can also be customized in detail,
> when to mail, etc.) and optionally
That's kind of a general setup, Stefan. Sending an email to the commiter
that broke the build with details of the build process, as well sending an
email to a mailing list.
I'll be looking into this Jenkins issue (JENKINS-5931). Maybe having an
access control based on IRC operators and voices?
On
Hi:
On 03 Nov 2011, at 20:15, Ferenc Kovacs wrote:
> The usual setup is that you have a mailing list/alias which always gets a
> mail about the build results (which can also be customized in detail, when to
> mail, etc.) and optionally you can notify the person whose commit break the
> build.
On Thu, Nov 3, 2011 at 7:43 PM, Stefan Marr wrote:
> Hi Ferenc:
>
> On 03 Nov 2011, at 19:01, Ferenc Kovacs wrote:
>
> > Of course there are ways to improve the current setup, I listed those
> ideas
> > at https://wiki.php.net/rfc/jenkins#future_plans
>
> Very nice.
> I don't know Jenkins, but wo
Yes, it is. But not only email notifications are possible, other
interesting integrations are possible. For example, Jabber.
https://wiki.jenkins-ci.org/display/JENKINS/Instant+Messaging+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin
On Thu, Nov 3, 2011 at 4:43 PM, Stefan Marr
Hi Ferenc:
On 03 Nov 2011, at 19:01, Ferenc Kovacs wrote:
> Of course there are ways to improve the current setup, I listed those ideas
> at https://wiki.php.net/rfc/jenkins#future_plans
Very nice.
I don't know Jenkins, but would it be possible to mail the author of a change
in case it breaks s
On Thu, Nov 3, 2011 at 6:10 PM, Klaus Silveira wrote:
> What are the current obstacles in a possible Jenkins implementation for
> the PHP codebase?
>
>
> --
> Klaus Silveira
> (011) 8564-2492
> www.klaussilveira.com
>
Sorry, I don't really follow you.
As I mentioned in my previous email and the R
What are the current obstacles in a possible Jenkins implementation for the
PHP codebase?
--
Klaus Silveira
(011) 8564-2492
www.klaussilveira.com
On Thu, Nov 3, 2011 at 1:46 AM, Ferenc Kovacs wrote:
>
>
> On Wed, Sep 7, 2011 at 11:29 AM, Hannes Magnusson <
> hannes.magnus...@gmail.com> wrote:
>
>> On Wed, Sep 7, 2011 at 03:53, Ferenc Kovacs wrote:
>> > On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev
>> wrote:
>> >> Hi!
>> >>
>> >> Since we
On Wed, Sep 7, 2011 at 11:29 AM, Hannes Magnusson <
hannes.magnus...@gmail.com> wrote:
> On Wed, Sep 7, 2011 at 03:53, Ferenc Kovacs wrote:
> > On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev
> wrote:
> >> Hi!
> >>
> >> Since we started to pay real attention to our unit tests now, I wonder
> if we
On Wed, Sep 7, 2011 at 03:53, Ferenc Kovacs wrote:
> On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev wrote:
>> Hi!
>>
>> Since we started to pay real attention to our unit tests now, I wonder if we
>> could set up some kind of frequently-running CI system that could be used to
>> screen commits and
hi Stas,
A new box is being setup with numerous VMs (Dan is on it). Each of of
them will cover one supported platform (debian, rh, bsd, win) and will
run the builds and tests using rmtools in controlled environment, like
what I began to do with windows a while back already. Build and tests
log wil
On Wed, Sep 7, 2011 at 3:29 AM, Stas Malyshev wrote:
> Hi!
>
> Since we started to pay real attention to our unit tests now, I wonder if we
> could set up some kind of frequently-running CI system that could be used to
> screen commits and identify breakage early? That'd help with 5.4 process I
>
+1
thanks
2011/9/7 Stas Malyshev :
> Hi!
>
> Since we started to pay real attention to our unit tests now, I wonder if we
> could set up some kind of frequently-running CI system that could be used to
> screen commits and identify breakage early? That'd help with 5.4 process I
> think.
> We have
Hi!
Since we started to pay real attention to our unit tests now, I wonder
if we could set up some kind of frequently-running CI system that could
be used to screen commits and identify breakage early? That'd help with
5.4 process I think.
We have http://gcov.php.net/ but it doesn't run with t
40 matches
Mail list logo
