Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75800 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43508 invoked from network); 21 Jul 2014 14:19:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2014 14:19:18 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.212.180 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:63308] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4D/18-01457-2612DC35 for ; Mon, 21 Jul 2014 10:19:16 -0400 Received: by mail-wi0-f180.google.com with SMTP id n3so4170509wiv.13 for ; Mon, 21 Jul 2014 07:19:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=P5bC82g7jyu6gA1J7eTYVWdZnNSqoW3jYlGx+1I4Kmo=; b=V/yjTmg07CbucBGUNn2RO1sr4laC88kiX0Hc1KQ8fGUkJlq0LzYPt7IsrTqlLYHkhF Goie8i7J35PWT9F4aFjCxMpGbfGE6ch36ZSDAkZoWMKz5MvIzsrbj/PF4XkdvraLIl6L 35hcG2UU3Dfd5ZnrYGG7M1XgUWLskF28+TZZk21mi0+0ticiyI5w8cbxRXT5RzDoUXaI Xye4nvy+oxu9vYFzl23/DpEBDelglKuOaRdBNK/3YXCzJTGncAEpZ7FHIMF3IJnyB8lm Y6jJiOXD+M8YtfnqBIftYctBcdcm4bXuOEqON50iifTjpesz+aCSgk3bxmSuEId+zlrH XGAg== X-Gm-Message-State: ALoCoQlXgmJjF4Y1HZ9cgVmlIVnbykFtQLsIDiKxLI8XCCZ/5GJTN0oyTc3ACFgFEF7Uss4cv0Wo MIME-Version: 1.0 X-Received: by 10.180.182.67 with SMTP id ec3mr4880507wic.21.1405952351557; Mon, 21 Jul 2014 07:19:11 -0700 (PDT) Received: by 10.194.13.164 with HTTP; Mon, 21 Jul 2014 07:19:11 -0700 (PDT) X-Originating-IP: [93.129.110.210] In-Reply-To: References: <2de3e71e35addbf16b2dc622f4c81eff@mail.gmail.com> <53CCD9BB.6060108@php.net> <53CCE669.8080403@beccati.com> Date: Mon, 21 Jul 2014 16:19:11 +0200 Message-ID: To: Dmitry Stogov Cc: Matteo Beccati , PHP Internals , Sebastian Bergmann Content-Type: multipart/alternative; boundary=047d7b5dbcda7c72f304feb4ca6a Subject: Re: [PHP-DEV] RFC: Move phpng to master From: kontakt@beberlei.de (Benjamin Eberlei) --047d7b5dbcda7c72f304feb4ca6a Content-Type: text/plain; charset=UTF-8 On Mon, Jul 21, 2014 at 12:41 PM, Dmitry Stogov wrote: > Hi Matteo, > > We have very limited forces to test everything. Once we we have bug reports > we may look into the problems and fix them. > Wouldn't it be super easy to use the HHVM team infrastructure to test a version against various PHP projects testsuites? I can't imagine it would take longer than a few hours to adjust this to PHPs needs. > > Thanks. Dmitry. > > > On Mon, Jul 21, 2014 at 2:07 PM, Matteo Beccati wrote: > > > On 21/07/2014 11:13, Sebastian Bergmann wrote: > > > Am 21.07.2014 10:33, schrieb Zeev Suraski: > > >> Regarding Dmitry saying that phpng is an experimental branch - that > was > > a > > >> couple of months ago. It evolved, it runs apps in parity with 5.6, > and > > it's > > >> fine to move it to master right now. The alternative - developing 5.7 > > on > > >> master and creating a synchronization hell - sounds like a horrible > > course > > >> of action. > > > > > > I was not able to run PHPUnit using PHPNG at all back when it was > first > > > announced. > > > > > > I was able to run PHPUnit 4.3 (master)'s test suite using PHPNG last > > > week, btw. Only one test fails (due to a change in the output of > > > print_r() for SplObjectStorage IIRC). This tells me that there was a > lot > > > of progress :-) > > > > I have temporarily re-enabled the phpng jobs on my CI server to assess > > the current situation. > > > > I can confirm that just one test is failing with PHPUnit master. It > > seems that print_r is not displaying StdClass properties as it used to: > > > > > > > https://revive.beccati.com/bamboo/browse/PHP-PHPUN-PHPNG-55/test/case/11800493 > > > > > > On the other hand Doctrine master can't even run the entire test suite > > due to: > > > > Fatal error: Call to a member function getConfiguration() on null in > > > > > /home/atlassian/bamboo/xml-data/build-dir/PHP-DOCTR-PHPNG/tests/Doctrine/Tests/OrmFunctionalTestCase.php > > on line 482 > > > > (pretty sure it's not a null there: a var_dump before the call tells me > > it's an object) > > > > https://revive.beccati.com/bamboo/browse/PHP-DOCTR-PHPNG-52/log > > > > > > The Revive Adserver test suite fails miserably (86+ out of 274 test > > files), mostly due to errors like: > > > > > > > /home/atlassian/bamboo/xml-data/build-dir/PHP-SRC3-BUIL/Zend/zend_hash.c(1369) > > : ht=0x29c7aa8 is already destroyed > > > > and some "Call to a member function" errors on object variables that are > > mysteriously seen as null. > > > > https://revive.beccati.com/bamboo/browse/REV-LP-PNGP-64 > > > > There's lots of legacy code in there and it has proved to be useful in > > past to catch a few uncommon segmentation faults. I'm pretty sure that > > there are plenty other applications that can't work with phpng as it is > > now. > > > > To be honest I don't think we're anywhere near the point where it's safe > > to merge phpng to master. > > > > Also, one thing that might have been overlooked is that merging phpng to > > master would completely bypass the voting phase on > > https://wiki.php.net/rfc/fast_zpp > > > > > > Cheers > > -- > > Matteo Beccati > > > > Development & Consulting - http://www.beccati.com/ > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > --047d7b5dbcda7c72f304feb4ca6a--