From: Eric Wong <e@80x24.org>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Git Users <git@vger.kernel.org>, Luke Diamand <luke@diamand.org>
Subject: Re: [BUG] t9801 and t9803 broken on next
Date: Fri, 13 May 2016 10:36:21 +0000 [thread overview]
Message-ID: <20160513103621.GA12329@dcvr.yhbt.net> (raw)
In-Reply-To: <3A110437-F778-42E2-A987-86B4EAB3D963@gmail.com>
Lars Schneider <larsxschneider@gmail.com> wrote:
> Hi,
>
> t9801 and t9803 seem to be broken on next. A quick bisect indicates that d9545c7
> "fast-import: implement unpack limit" might be the reason. (@gmane/292562).
>
> Did anyone look into that already?
Just took a look (no p4, so couldn't run tests) and I guess it's
because the default changed and it doesn't generate tiny packs.
The easiest change is probably to call:
git config fastimport.unpackLimit 0
during setup like t9300 now does.
next prev parent reply other threads:[~2016-05-13 10:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 10:02 [BUG] t9801 and t9803 broken on next Lars Schneider
2016-05-13 10:36 ` Eric Wong [this message]
2016-05-13 16:37 ` Junio C Hamano
2016-05-14 8:04 ` Lars Schneider
2016-05-14 18:15 ` Junio C Hamano
2016-05-17 8:07 ` Lars Schneider
2016-05-17 9:13 ` Eric Wong
2016-05-17 12:13 ` Jeff King
2016-05-19 8:19 ` Lars Schneider
2016-05-19 17:03 ` Junio C Hamano
2016-05-19 17:32 ` Lars Schneider
2016-05-25 22:49 ` Eric Wong
2016-05-25 22:54 ` [RFC] fast-import: invalidate pack_id references after loosening Eric Wong
2016-05-25 23:09 ` Jeff King
2016-05-26 8:02 ` Eric Wong
2016-05-26 14:16 ` Jeff King
2016-05-28 0:20 ` Eric Wong
2016-05-25 22:56 ` [BUG] t9801 and t9803 broken on next Jeff King
2016-05-17 8:35 ` Luke Diamand
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=20160513103621.GA12329@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=luke@diamand.org \
/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).