From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nigel Magnay <nigel.magnay@gmail.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: [JGIT] maven build fails on OS X
Date: Fri, 6 Feb 2009 07:31:55 -0800 [thread overview]
Message-ID: <20090206153155.GL26880@spearce.org> (raw)
In-Reply-To: <320075ff0902060708m5ec566b9g755829c25c7727d8@mail.gmail.com>
Nigel Magnay <nigel.magnay@gmail.com> wrote:
> I don't know if this is known about - I get failures running the m2
> build for jgit:
Yup.
> Failed tests:
> testParse_implicit_mixed_encoded(org.spearce.jgit.revwalk.RevCommitParseTest)
> testParse_explicit_bad_encoded(org.spearce.jgit.revwalk.RevCommitParseTest)
> testParse_implicit_mixed_encoded(org.spearce.jgit.revwalk.RevTagParseTest)
> testParse_explicit_bad_encoded(org.spearce.jgit.revwalk.RevTagParseTest)
> testDequote_OctalAll(org.spearce.jgit.util.QuotedStringGitPathStyleTest)
> testDequote_Latin1(org.spearce.jgit.util.QuotedStringGitPathStyleTest)
> testDequote_RawLatin1(org.spearce.jgit.util.QuotedStringGitPathStyleTest)
> testGetText_DiffCc(org.spearce.jgit.patch.GetTextTest)
>
> Curiously, the tests work in eclipse and from ./make_jgit.sh - I
> suspect some environment setting with the mac's charset.
make_jgit.sh doesn't run tests. But Eclipse does, and as you state,
I have also seen these pass in Eclipse but fail from m2.
What's even more curious is look at the surefire report files for
these tests. The actual result looks correct, the expected result
looks wrong. I think m2 miscompiled the Java sources for the tests
somehow and produced incorrect literal strings which are used for
the expected values in the tests.
I don't see these failures on Linux, from either Eclipse or Maven.
> I can try and fix it if it's new, but I wanted to check first..
I've looked at it and gave up. I don't know what Maven is doing here
on the Mac. Maybe fresh eyes will have a better chance at fixing it.
My experience with Maven is it works about 5% of the time, and the
other 95% of the time you have to work around it by skipping tests,
or by writing massive blocks of XML in your pom.xml file, or by
redesigning your entire project directory structure and revision
control system to use SVN instead of Git.
--
Shawn.
next prev parent reply other threads:[~2009-02-06 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 15:08 [JGIT] maven build fails on OS X Nigel Magnay
2009-02-06 15:31 ` Shawn O. Pearce [this message]
2009-02-06 20:08 ` Nigel Magnay
2009-02-06 21:07 ` Robin Rosenberg
2009-02-06 20:54 ` Robin Rosenberg
2009-02-06 21:12 ` Nigel Magnay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090206153155.GL26880@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).