Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Crash while syncing
Date: Sat, 29 Aug 2009 19:05:33 +0200	[thread overview]
Message-ID: <cd67f63a0908291005m5a53b2cei71bfa48e4bc1d658@mail.gmail.com> (raw)
In-Reply-To: <1251564961-sup-5855@zyrg.net>

On Sat, Aug 29, 2009 at 6:59 PM, Rich Lane<rlane at club.cc.cmu.edu> wrote:
> Excerpts from Nicolas Pouillard's message of Sat Aug 29 12:45:29 -0400 2009:
>> > Are you using the Flint or Chert Xapian backend?
>>
>> The Chert one.
>
> Could you try it with Flint? I've seen this (nondeterministic) bug when
> using Chert.

I was currently running it again with no problems so far.

Are the nondeterministic bugs only during sync?

Chert is supposed to faster?

Thanks for your help,

-- 
Nicolas Pouillard


  reply	other threads:[~2009-08-29 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29  9:18 Nicolas Pouillard
2009-08-29 12:03 ` Nicolas Pouillard
2009-08-29 16:25   ` Rich Lane
2009-08-29 16:45     ` Nicolas Pouillard
2009-08-29 16:59       ` Rich Lane
2009-08-29 17:05         ` Nicolas Pouillard [this message]
2009-08-30  0:22           ` Rich Lane

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=cd67f63a0908291005m5a53b2cei71bfa48e4bc1d658@mail.gmail.com \
    --to=nicolas.pouillard@gmail.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