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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html