git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Thomas Braun <thomas.braun@virtuell-zuhause.de>,
	git@vger.kernel.org, msysGit <msysgit@googlegroups.com>,
	git-owner@vger.kernel.org
Subject: Re: Issue: repack semi-frequently fails on Windows (msysgit) - suspecting file descriptor issues
Date: Thu, 16 Apr 2015 15:07:46 +0200	[thread overview]
Message-ID: <f046adea6791865f97f6d76b0dae01bc@www.dscho.org> (raw)
In-Reply-To: <20150416123552.GA825@rhlx01.hs-esslingen.de>

Hi Andreas,

On 2015-04-16 14:35, Andreas Mohr wrote:
> On Thu, Apr 16, 2015 at 01:48:46PM +0200, Andreas Mohr wrote:
>> OK, at this point in time it's my turn to actually verify
>> that indeed it's NOT the virus scanner:
>> - generate rebase-heavy activity
>> - update
>> - hit issue
>> - unload virus (~ scanner?? I'm unsure on exact terminology to be used ;-)
>> - update
>> - profit!?
> 
> Despite trying hard (generating a lot of activity, with different repo
> projects even)
> I cannot reproduce it in a timely manner,
> thus I'll have to wait until repo state has degraded in a sufficient manner
> for such a larger repack with that issue to occur again
> (probably a matter of weeks).
> Once it happens, I will:
> - ensure keeping a copy of the entire (problematic-state) repo, and
> verify reproducibility of its (copied/preserved) breakage
> - unload virus and do other tests
> - report back

I guess the best way to trigger it is by ensuring that a lot of loose objects are accumulated, e.g. by running

```sh
i=$(date +%s)
j=0
while test $j -lt 9999
do
    echo "test $(($i+$j))" git hash-object -w --stdin
    j=$(($j+1))
done
```

Ciao,
Johannes

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2015-04-16 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 10:03 Issue: repack semi-frequently fails on Windows (msysgit) - suspecting file descriptor issues Andreas Mohr
2015-04-16 11:10 ` Thomas Braun
2015-04-16 11:31   ` Johannes Schindelin
2015-04-16 11:42     ` Andreas Mohr
2015-04-16 11:48       ` Andreas Mohr
2015-04-16 12:35         ` Andreas Mohr
2015-04-16 13:07           ` Johannes Schindelin [this message]
2015-04-16 11:35   ` Andreas Mohr
2015-04-16 15:28     ` Jeff King
2015-04-16 15:48       ` Johannes Schindelin
2015-04-16 15:56         ` David Miller
2015-04-16 20:56         ` Andreas Mohr
2015-04-23  6:52       ` rupert thurner

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=f046adea6791865f97f6d76b0dae01bc@www.dscho.org \
    --to=johannes.schindelin@gmx.de \
    --cc=andi@lisas.de \
    --cc=git-owner@vger.kernel.org \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.com \
    --cc=thomas.braun@virtuell-zuhause.de \
    /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).