git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Tan <jonathantanmy@google.com>,
	Jeff Hostetler <jeffhost@microsoft.com>,
	GIT Mailing-list <git@vger.kernel.org>
Subject: Test failures on 'pu' branch
Date: Wed, 8 Nov 2017 20:28:48 +0000	[thread overview]
Message-ID: <cf38b57d-1424-0776-b67f-8cfd24e087bb@ramsayjones.plus.com> (raw)

Hi Junio,

You are probably already aware, but just in case, the 'pu' branch
fails the testsuite for me as follows:

$ tail -18 ptest-out
Test Summary Report
-------------------
t5300-pack-object.sh                             (Wstat: 256 Tests: 40 Failed: 2)
  Failed tests:  36-37
  Non-zero exit status: 1
t5500-fetch-pack.sh                              (Wstat: 256 Tests: 355 Failed: 6)
  Failed tests:  350-355
  Non-zero exit status: 1
t5601-clone.sh                                   (Wstat: 256 Tests: 102 Failed: 4)
  Failed tests:  99-102
  Non-zero exit status: 1
Files=800, Tests=16964, 462 wallclock secs ( 4.57 usr  0.78 sys + 57.93 cusr 24.16 csys = 87.44 CPU)
Result: FAIL
Makefile:45: recipe for target 'prove' failed
make[1]: *** [prove] Error 1
make[1]: Leaving directory '/home/ramsay/git/t'
Makefile:2448: recipe for target 'test' failed
make: *** [test] Error 2
$ 

Looking at the first test failure in each file, the failures seems
to be related to the 'jh/partial-clone' branch.

Just FYI. Thanks.

ATB,
Ramsay Jones


             reply	other threads:[~2017-11-08 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 20:28 Ramsay Jones [this message]
2017-11-08 20:36 ` Test failures on 'pu' branch Stefan Beller
2017-11-08 22:10   ` Jeff Hostetler
2017-11-08 22:34   ` Ramsay Jones
2017-11-08 22:55     ` Ramsay Jones

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=cf38b57d-1424-0776-b67f-8cfd24e087bb@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jeffhost@microsoft.com \
    --cc=jonathantanmy@google.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).