Description: ------------ Two unit test failures when running your tests along with my code: VersionControl_Git_Object_CommitTest::testGetCreatedAt() Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:118 VersionControl_Git_Object_CommitTest::testGetCommittedAt( ) Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:151 VersionControl_Git_Object_CommitTest::testFetch() Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:184 Full output can be found in Output window. My full output is as follows: PHPUnit 3.4.15 by Sebastian Bergmann. ..F.fatal: ambiguous argument 'invalid': unknown revision or path not in the working tree. Use '--' to separate paths from revisions .F. 120 / 138 ................git: 'subcommand' is not a git-command. See 'git -- help'. .. Time: 8 seconds, Memory: 13.25Mb There were 3 failures: 1) VersionControl_Git_Object_CommitTest::testGetCreatedAt Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:118 2) VersionControl_Git_Object_CommitTest::testGetCommittedAt Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:151 3) VersionControl_Git_Object_CommitTest::testFetch Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -20100120101001 +20100121011001 VersionControl_Git_Object_CommitTest.php:184 FAILURES! Tests: 138, Assertions: 251, Failures: 3, Incomplete: 11. I'm running these alongside a project of mine, which can be found here: http://github.com/itrebal/DBS

I could confirm this problem. I think that the failed strings contain Escape-sequence.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. master: https://github.com/ebihara/VersionControl_Git/commit/ce1011b54cf311a27fe4664b10746e72c116a6b4 stable: https://github.com/ebihara/VersionControl_Git/commit/f0cf10340e0c09abfd4748da726bc2f65f66a772