Hi, Our attempt to run Drupal-8 today, disclosed at least 3 new problems. 2 of them must be already fixed, but I know we must have a lot of other problems uncovered by our test suite. Every new tested app my trigger something new. The more attention we draw now the better quality we will provide.
Instead of using FPM, especially for testing, it may make sense to run single FastCGI process $ sapi/cgi/php-cgi -b <socket> DEBUG build will report memory leaks to analyze memory corryption and leaks, it's also possible to run php under valgrind $ USE_ZEND_ALLOC=0 valgrind --leak-check=full sapi/cgi/php-cgi -b <socket> No any special web server configuration required, just configure it for FastCGI server on the <socket>. Then you may run FPM or FastCGI SAPI or even HHVM on the same <socket> without web server restart. Thanks. Dmitry. On Thu, Jan 22, 2015 at 9:39 PM, Matteo Beccati <p...@beccati.com> wrote: > On 22/01/2015 19:32, Levi Morrison wrote: > >> I had to quarantine a couple of tests in Doctrine and PHPUnit as they both >>> depend on the re-usage of the hashes returned by spl_object_hash(), which >>> shouldn't actually be depended upon (am I right dmitry?). >>> >> >> I'm not Dmitry, but I am fairly certain you should not rely on hashes >> being reused. >> > > I was quoting a quick discussion we had, that's why I mentioned him ;) > > To make my stament clearer, I meant "spl_object_hash re-using the hash of > an object that has been unset and garbage collected". > > TBH I don't recall what the PHPUnit test does, but I'm fairly sure that > the Doctrine2 tests uses such test to verify that there are no "leaks" > using a certain recommended pattern for batch operations (or something > along the lines). > > > > Cheers > -- > Matteo Beccati > > Development & Consulting - http://www.beccati.com/ >
