Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Anton Kolesov <Anton.Kolesov@synopsys.com>
Cc: Yao Qi <qiyaoltc@gmail.com>,
	 "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	 Francois Bedard <Francois.Bedard@synopsys.com>
Subject: Re: [PATCH] Import setenv and unsetenv from gnulib
Date: Thu, 06 Jul 2017 15:34:00 -0000	[thread overview]
Message-ID: <87tw2p4m0h.fsf@redhat.com> (raw)
In-Reply-To: <39A54937CC95F24AA2F794E2D2B66B135876E5CC@DE02WEMBXB.internal.synopsys.com>	(Anton Kolesov's message of "Wed, 5 Jul 2017 09:50:47 +0000")

On Wednesday, July 05 2017, Anton Kolesov wrote:

>> >>
>> >> Did you run regression test on x86-linux?  If there is no regression,
>> >> patches is good to me.
>> >
>> > If I run "make check-gdb", I don't see any obvious new errors from this
>> patch.
>> > Unfortunately results are a little bit volatile - some tests
>> > sporadically fail even if I run them with same GDB build and sources,
>> > even without this patch - I've run testsuite five times and got five similar,
>> but different results.
>> 
>> Yeah, our testsuite has racy fails which are well known.  What are the tests
>> that fail sporadically?
>
> - gdb.base/checkpoint-ns.exp: break
> - gdb.base/checkpoint.exp: break2 with many checkpoints
> - gdb.btrace/exception.exp: indented
> - Several consequtive tests in gdb.btrace/rn-dl-bind.exp

These don't ring any bells for me, but since you're testing on MingW, it
may very well be that they're racy tests on this platform as well.  My
take is that if you can reproduce the exact failures without your patch,
then you can discard them as racy.

> - gdb.threads/process-dies-while-handling-bp.exp: non_stop=off (KFAIL became
> PASS with my patch).

This one is a known racy test.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2017-07-06 15:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 10:04 [PATCH] Fix build breakage on MinGW due to missing setenv Anton Kolesov
2017-07-03 11:21 ` Yao Qi
2017-07-03 15:26   ` Sergio Durigan Junior
2017-07-03 16:27     ` [PATCH] Import setenv and unsetenv from gnulib Anton Kolesov
2017-07-03 19:35       ` Sergio Durigan Junior
2017-07-04 10:20       ` Yao Qi
2017-07-04 18:06         ` Anton Kolesov
     [not found]           ` <8737ac6j91.fsf@redhat.com>
2017-07-05  9:50             ` Anton Kolesov
2017-07-06 15:34               ` Sergio Durigan Junior [this message]
2017-07-05  9:56           ` Pedro Alves
2017-07-05 10:32             ` Anton Kolesov
2017-07-07  8:24           ` Yao Qi
2017-07-07  9:35             ` Anton Kolesov

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=87tw2p4m0h.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=Anton.Kolesov@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@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