git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: git-svn tests fail since 1.7.2.2
Date: Thu, 28 Oct 2010 22:32:54 +0200	[thread overview]
Message-ID: <20101028223254.25c0241a@pc09.procura.nl> (raw)
In-Reply-To: <20101028175648.GA14212@burratino>

On Thu, 28 Oct 2010 12:56:48 -0500, Jonathan Nieder
<jrnieder@gmail.com> wrote:

> Hi,
> 
> H.Merijn Brand wrote [snipped somewhat]:
> 
> > Up to and including 1.7.2.1, all went smooth and fine, but as of
> > 1.7.2.2 (and 1.7.3.1 and 1.7.3.2), the tests started to fail on svn
> > issues.
> >
> > t9101-git-svn-props.sh                           (Wstat: 256 Tests: 26 Failed: 3)
> >   Failed tests:  24-26
> > t9143-git-svn-gc.sh                              (Wstat: 256 Tests: 11 Failed: 1)
> >   Failed test:  10
> >
> > These tests fail on *all* my Linux boxes, which happen to be OpenSUSE
> > ranging from 11.0 to 11.3.
> >
> > OpenSUSE 11.0/64:
> > + svn, version 1.5.7 (r36142)
> > 
> > OpenSUSE 11.2/64:
> > + svn, version 1.6.6 (r40053)
> > 
> > OpenSUSE 11.3/32:
> > + svn, version 1.6.9 (r901367)
> 
> Any idea what error message or command they fail at?  Useful commands
> to try might be
> 
>  sh t9101-git-svn-props.sh -v

ok 23 - test show-ignore

expecting success:
        git svn fetch && git pull . remotes/git-svn &&
        git svn create-ignore &&
        cmp ./.gitignore create-ignore.expect &&
        cmp ./deeply/.gitignore create-ignore.expect &&
        cmp ./deeply/nested/.gitignore create-ignore.expect &&
        cmp ./deeply/nested/directory/.gitignore create-ignore.expect &&
        git ls-files -s | grep gitignore | cmp - create-ignore-index.expect

        A       deeply/nested/directory/.keep
r8 = ddf07d64e9879c7d8f730b781596e1a6cf5d413b (refs/remotes/git-svn)
From .
 * remote branch     git-svn    -> FETCH_HEAD
Updating eff953b..ddf07d6
Fast-forward
 0 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 deeply/nested/directory/.keep
-: No such file or directory
not ok - 24 test create-ignore
#
#               git svn fetch && git pull . remotes/git-svn &&
#               git svn create-ignore &&
#               cmp ./.gitignore create-ignore.expect &&
#               cmp ./deeply/.gitignore create-ignore.expect &&
#               cmp ./deeply/nested/.gitignore create-ignore.expect &&
#               cmp ./deeply/nested/directory/.gitignore create-ignore.expect &&
#               git ls-files -s | grep gitignore | cmp - create-ignore-index.expect
#

expecting success:
        git svn propget svn:ignore . | cmp - prop.expect &&
        cd deeply &&
        git svn propget svn:ignore . | cmp - ../prop.expect &&
        git svn propget svn:entry:committed-rev nested/directory/.keep    | cmp - ../prop2.expect &&
        git svn propget svn:ignore .. | cmp - ../prop.expect &&
        git svn propget svn:ignore nested/ | cmp - ../prop.expect &&
        git svn propget svn:ignore ./nested | cmp - ../prop.expect &&
        git svn propget svn:ignore .././deeply/nested | cmp - ../prop.expect

-: No such file or directory
error: git-svn died of signal 13
not ok - 25 test propget
#
#               git svn propget svn:ignore . | cmp - prop.expect &&
#               cd deeply &&
#               git svn propget svn:ignore . | cmp - ../prop.expect &&
#               git svn propget svn:entry:committed-rev nested/directory/.keep   | cmp - ../prop2.expect &&
#               git svn propget svn:ignore .. | cmp - ../prop.expect &&
#               git svn propget svn:ignore nested/ | cmp - ../prop.expect &&
#               git svn propget svn:ignore ./nested | cmp - ../prop.expect &&
#               git svn propget svn:ignore .././deeply/nested | cmp - ../prop.expect
#

expecting success:
        git svn proplist . | cmp - prop.expect &&
        git svn proplist nested/directory/.keep | cmp - prop2.expect

-: No such file or directory
error: git-svn died of signal 13
not ok - 26 test proplist
#
#               git svn proplist . | cmp - prop.expect &&
#               git svn proplist nested/directory/.keep | cmp - prop2.expect
#

# failed 3 among 26 test(s)
1..26
Exit 1

Right, If I would have thought of that myself, I would not have had to report
the issue. My system seems to have a non-standard "cmp" that seems to
have been chosen over the system one. That cmp does not handle -.

Problem solved:

ok 26 - test proplist

# passed all 26 test(s)
1..26

> and
> 
>  sh -x t9101-git-svn-props.sh -v -i
> 
> Thanks for reporting,
> Jonathan


-- 
H.Merijn Brand  http://tux.nl      Perl Monger  http://amsterdam.pm.org/
using 5.00307 through 5.12 and porting perl5.13.x on HP-UX 10.20, 11.00,
11.11, 11.23 and 11.31, OpenSuSE 10.1, 11.0 .. 11.3 and AIX 5.2 and 5.3.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/

      reply	other threads:[~2010-10-28 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 10:28 git-svn tests fail since 1.7.2.2 H.Merijn Brand
2010-10-28 15:49 ` Mathias Lafeldt
2010-10-28 17:56 ` Jonathan Nieder
2010-10-28 20:32   ` H.Merijn Brand [this message]

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=20101028223254.25c0241a@pc09.procura.nl \
    --to=h.m.brand@xs4all.nl \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=normalperson@yhbt.net \
    /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).