Actually I did test with all of the 1.9 releases including the release-1.9 branch, although I was mistaken about the issue existing in 1.9.0 (I don't expect that you've really tried to reproduce this against different versions).
(I don't expect that you've really tested with 5 different releases the same time)
Thomas, please comment on the issue rather than on whether or not you think the reporter is being dishonest. Issue reporters will mostly not bother posting again if you have an attitude problem.
Here is your further info:
Zend_Translate_Adapter_IniTest::testCreate()
PHP Fatal error: Unsupported operand types in /data/php5/ZendFramework/library/Zend/Translate/Adapter.php on line 482
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. require() /usr/bin/phpunit:44
PHP 3. PHPUnit_TextUI_Command::main() /usr/share/php5/PEAR/PHPUnit/TextUI/Command.php:718
PHP 4. PHPUnit_TextUI_TestRunner->doRun() /usr/share/php5/PEAR/PHPUnit/TextUI/Command.php:131
PHP 5. PHPUnit_Framework_TestSuite->run() /usr/share/php5/PEAR/PHPUnit/TextUI/TestRunner.php:324
PHP 6. PHPUnit_Framework_TestSuite->run() /usr/share/php5/PEAR/PHPUnit/Framework/TestSuite.php:636
PHP 7. PHPUnit_Framework_TestSuite->runTest() /usr/share/php5/PEAR/PHPUnit/Framework/TestSuite.php:673
PHP 8. PHPUnit_Framework_TestCase->run() /usr/share/php5/PEAR/PHPUnit/Framework/TestSuite.php:692
PHP 9. PHPUnit_Framework_TestResult->run() /usr/share/php5/PEAR/PHPUnit/Framework/TestCase.php:375
PHP 10. PHPUnit_Framework_TestCase->runBare() /usr/share/php5/PEAR/PHPUnit/Framework/TestResult.php:609
PHP 11. PHPUnit_Framework_TestCase->runTest() /usr/share/php5/PEAR/PHPUnit/Framework/TestCase.php:401
PHP 12. ReflectionMethod->invoke() /usr/share/php5/PEAR/PHPUnit/Framework/TestCase.php:486
PHP 13. Zend_Translate_Adapter_IniTest->testCreate() /data/php5/ZendFramework/tests/Zend/Translate/Adapter/IniTest.php:0
PHP 14. Zend_Translate_Adapter_Ini->__construct() /data/php5/ZendFramework/tests/Zend/Translate/Adapter/IniTest.php:67
PHP 15. Zend_Translate_Adapter->__construct() /data/php5/ZendFramework/library/Zend/Translate/Adapter/Ini.php:48
PHP 16. Zend_Translate_Adapter->addTranslation() /data/php5/ZendFramework/library/Zend/Translate/Adapter.php:117
PHP 17. Zend_Translate_Adapter->_addTranslationData() /data/php5/ZendFramework/library/Zend/Translate/Adapter.php:212
OS | PHP Release | ZF Release | Issue occurs
----------+-------------+-------------+-------------
GNU/Linux | 5.2.11 | 1.9.1-1.9.4 | No
GNU/Linux | 5.3.0 | 1.9.1-1.9.4 | Yes
GNU/Linux | 5.3.0 | Trunk | No
The problem lies in the structure of the two arrays being merged, here is the statement where the issue occurs.
$this->_translate[$key] = $temp[$key] + $this->_translate[$key];
In PHP 5.3.0 the value of $temp[$key] is null whereas in PHP 5.2.x it is an empty array. This is a result of the differing return value of parse_ini_file() between PHP versions.
And no, trunk has no BC issue, but new features are not allowed to be integrated into branch. Only bugs are allowed to be branched. The changeset you pointed to is no bug fix but a feature enhancement and this could lead to a BC breaking behaviour as features must not change between mini releases.
I'm confused, there is no BC issue but the changeset can't be merged because there is a BC issue?
The changeset is http://framework.zend.com/code/browse/Standard_Library/standard/trunk/library/Zend/Translate/Adapter.php?r1=17760&r2=17784
The conditional check made against the array operation in the _addTranslationData() method in this changeset addresses the broken test case when using PHP 5.3. I don't understand why this code change was added in the same commit as the other changes which address #ZF-7508, the changes are entirely unrelated.
Not reproducable, please give additional infos:
OS, php release, ZF release (I don't expect that you've really tested with 5 different releases the same time), the complete error/exception which is thrown/returned
And no, trunk has no BC issue, but new features are not allowed to be integrated into branch. Only bugs are allowed to be branched. The changeset you pointed to is no bug fix but a feature enhancement and this could lead to a BC breaking behaviour as features must not change between mini releases.
And no, unit test problems are not intentionally fatal problems. Especially when there is one error within 400 tests of one component.