PHP 5.5 can't fail anymore

[Slamdunk]

With the release of the first stable PHP 5.5 version, travis is no more allowed to fail.

[marc-mabe]

As you can see the travis is on PHP 5.5.0RC3 - so we have to wait as long as travis updated the PHP version

[Slamdunk]

PHP 5.5 is on stable now in travis:

PHP 5.5.0 (cli) (built: Jun 21 2013 15:37:05)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.5.0-dev, Copyright (c) 1998-2013 Zend Technologies
    with Zend OPcache v7.0.2-dev, Copyright (c) 1999-2013, by Zend Technologies
    with Xdebug v2.2.3, Copyright (c) 2002-2013, by Derick Rethans

[weierophinney]

@Slamdunk Are you willing to fix the issues on 5.5 as well? (Just kidding!) Thanks for the update; will merge later.

[mwillbanks]

@weierophinney should we merge this now or fix the failing test first :)

[Slamdunk]

@mwillbanks definitely merge: tests should be fixed only when they fail. A red test in a green testsuite run is NOT a fail 😉

[weierophinney]

I'd argue that as part of merging, we should attempt to address the failing tests.

The problem is: I've tried. When I ran the tests locally, they ran fine, and I could not reproduce the failures seen on Travis. This means we likely need to skip them in Travis -- but I don't like that solution, in case there's something fundamentally wrong.

@mwillbanks Thoughts?

[mwillbanks]

@weierophinney when i started running them last night I had a ton of failures; way more than travis did (likely my configuration and extensions) so I was attempting to hone those in first but ran out of time last night. I might boot up a machine today just for running some of the tests.

[Maks3w]

At this moment there is only one "passive" test failure with PHP 5.5

https://travis-ci.org/zendframework/zf2/jobs/9172993#L546

Some volunteer for fix it?

[marc-mabe]

This is a test for not running into an infinite loop on self references. PHP < 5.5 automatically skip the first found self reference with null but PHP >= 5.5 they write in the man 5.5.0 depth parameter was added.

But using json_encode has other issues I think. (What if you don't log UTF-8 messages?)
Could we remove json_encode and format it using print_r or var_export eventually with an additional preg_replace to reformat line breaks?

EDIT Or of course serialize could be another candidate, too.