Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: bug-readline@gnu.org, gdb-patches@sourceware.org,
		Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] Fix testsuite annotate-quit race (PR 544)
Date: Wed, 19 Mar 2008 09:56:00 -0000	[thread overview]
Message-ID: <18400.58139.937426.478457@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080319092335.GA1995@host0.dyn.jankratochvil.net>

 > * I still face testsuite results flutter making the day-to-day regressions
 >   evaluations expensive.  Most of the flutters are fixed in gdb-6.8 but still
 >   some of them remain, this fix is for one of them.
 > 
 >   * I do not care much if it FAILs or PASSes but it must not flutter.
 > 
 > * I found it is a known PR 544 only after I fixed it.
 > 
 > * I fixed it as it was a nuisance reported by the courtesy of Roland McGrath.
 > 
 > * As the SIGINT blocking in RL_REDISPLAY fixes the race (1 of 10 cases to 0 of
 >   350 cases during my test) I find it a proof there must be some race.
 >   In fact if you check that RL_REDISPLAY modifies a lot of global variables
 >   being tangled by SIGINT-handler-called RL_FREE_LINE_STATE it is clear some
 >   locking is missing there.
 > 
 > * Sure I am fine to keep the patch in the local branch.

I find it to resolve such matters easier by talking person to person than
communicating by e-mail, but here goes:

You say "I am fine to keep the patch in the local branch." but from the
preceding points it sounds anything but fine.  I don't have the understanding
of readline to make a judgement on your patch but I am just worried it will
break something for Emacs just as a previous change that you and Daniel made to
readline did.

It appear to me that the only problem this FAIL is causing is with the actual
running of the testsuite.  I would be quite happy if this test was just
removed.  Would that work for everyone else?

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-03-19  9:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 22:55 Jan Kratochvil
2008-03-18 23:18 ` Daniel Jacobowitz
2008-03-19  8:11   ` Jan Kratochvil
2008-03-19  8:46     ` Nick Roberts
2008-03-19  9:31       ` Jan Kratochvil
2008-03-19  9:56         ` Nick Roberts [this message]
2008-03-19 10:13           ` Jan Kratochvil
2008-03-21 20:45     ` Jan Kratochvil
2008-03-21 21:04       ` Daniel Jacobowitz
2008-03-21 21:45         ` Daniel Jacobowitz
2008-03-23 11:01           ` Nick Roberts
2008-03-23 16:30             ` Daniel Jacobowitz
2008-03-23 16:44               ` Jan Kratochvil
2008-03-23 17:30                 ` Daniel Jacobowitz
2008-03-24  0:07                   ` Nick Roberts
2008-03-24  2:58                     ` Daniel Jacobowitz
2008-03-24  7:42                       ` Jan Kratochvil
2008-03-24 12:00                         ` Daniel Jacobowitz
2008-03-24 13:03                           ` Jan Kratochvil
2008-03-24 13:27                             ` Daniel Jacobowitz
2008-03-25  1:02                       ` Chet Ramey
2008-03-25  2:53                         ` Daniel Jacobowitz
2008-03-25 15:56                           ` Chet Ramey

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=18400.58139.937426.478457@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=bug-readline@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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