Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: FAILs on x86?
Date: Thu, 27 Mar 2008 12:33:00 -0000	[thread overview]
Message-ID: <47EB9404.7010109@de.ibm.com> (raw)
In-Reply-To: <fsg3jg$fts$1@ger.gmane.org>

Vladimir Prus schrieb:
> Markus Deuling wrote:
> 
>> Daniel Jacobowitz schrieb:
>>> On Thu, Mar 27, 2008 at 12:37:03PM +0100, Markus Deuling wrote:
>>>> Hi,
>>>>
>>>> I see lots of FAILs on x86. Anyone else seeing this?
>>> Not me.  What's in gdb.log for a typical failure?
>>>
>> Nothing special, I think (I dont think its an environment problem). Just a lot of FAILs in
>> gdb.{base,cp,mi}. I posted a list of the FAILs that are new compared to a testrun some days ago
>> here:
>>
>> http://sourceware.org/ml/gdb-testers/2008-q1/msg00022.html
>>
>> As far as I see there were some commits to some areas where GDB test fails
>> now (gdb.cp, gdb.mi, dfp). If needed I can attach gdb.log
> 
> When were the tests run? gdb.mi failures are supposed to be fixed now.
> 
> - Volodya
> 

Today, just an hour ago. I currently re-run tests for ppc and spu.

-- 
  Markus Deuling
  GNU Toolchain for Linux on Cell BE
  deuling@de.ibm.com


  reply	other threads:[~2008-03-27 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 11:37 Markus Deuling
2008-03-27 11:51 ` Daniel Jacobowitz
2008-03-27 12:15   ` Markus Deuling
2008-03-27 12:23     ` Vladimir Prus
2008-03-27 12:33       ` Markus Deuling [this message]
2008-03-27 12:55         ` Vladimir Prus
2008-03-27 13:29           ` Markus Deuling
2008-03-27 13:40             ` Vladimir Prus
2008-03-27 13:51               ` Markus Deuling
2008-03-27 14:19                 ` Vladimir Prus
2008-03-27 12:44     ` Daniel Jacobowitz
2008-03-27 12:48       ` Markus Deuling
2008-03-27 13:04         ` Daniel Jacobowitz

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=47EB9404.7010109@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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