Description of problem: The build has reported 1 extra testsuite failures: ...build.log truncated.... TEST FAILURE: ../ext/date/tests/bug20382-2.diff -- 047+ ts = Monday 2037-09-28 17:17:17 NZDT 047- ts = Monday 2037-09-28 17:17:17 NZST -- ../ext/date/tests/bug20382-2.diff result ends. ...build.log truncated .... Version-Release number of selected component (if applicable): old-version : php-5.1.6-20.el5 new-version : php-5.1.6-20.el5_2.1 How reproducible: Compare old build log with new one. Actual results: Tests failed : 3 ( 0.1%) ( 0.3%) Expected results: Tests failed : 2 ( 0.1%) ( 0.2%)
To be clear, did this test fail with both the new and old versions of php? What version of the tzdata packaeg was used when running the test in each case?
> To be clear, did this test fail with both the new and old versions of php? no, only with new version. To be definite with new version there are 3 tests failed and with old version there are only 2 tests failed. This test is extra in new version : TEST FAILURE: ../ext/date/tests/bug20382-2.diff -- 047+ ts = Monday 2037-09-28 17:17:17 NZDT 047- ts = Monday 2037-09-28 17:17:17 NZST > What version of the tzdata packaeg was used when running the test in each case? tzdata noarch 2008b-3.el5 core 753 k
OK. It looks like this test case is wrong for the current tzdata, it has been fixed upstream. So the result is a false negative; I'm not sure why the test case wouldn't fail with the old packages. We can fix the test case for future updates.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0226.html