public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: frysk@sourceware.org
Subject: Re: Automated build-and-test summary report (2007/05/23)
Date: Wed, 30 May 2007 16:08:00 -0000	[thread overview]
Message-ID: <465D7CC2.9080603@redhat.com> (raw)
In-Reply-To: <20070530011241.GB14523@ca-server1.us.oracle.com>

Kris Van Hees wrote:
> Throughout the months the system has been in development, and then
> became fully functioning, we suffered through quite a few iterations of
> finding kernel problems relating to utrace.  More often than not, these
> were problems that others had not reported (either due to not testing on
> those configurations or otherwise).  We got quite a bit of traction on
> that and largely due to Roland's work, the situation improved a whole
> lot.
>   

To clarify.

The improvements to Frysk on Fedora Core 6 largely came about as a 
consequence of bugs identified by Roland, Moller, and myself when 
testing on RHEL 5 (the kernels were relatively close).  For instance, 
the need to re-implement the event-loop, that Red Hat undertook, was 
motivated by these bugs.

Andrew

  parent reply	other threads:[~2007-05-30 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 15:04 Kris Van Hees
2007-05-23 21:47 ` Andrew Cagney
2007-05-24  7:50   ` Kris Van Hees
2007-05-24 19:25     ` Andrew Cagney
2007-05-24 20:39       ` Kris Van Hees
2007-05-28 19:35         ` Andrew Cagney
2007-05-29 18:50           ` Andrew Cagney
2007-05-30 12:07             ` Kris Van Hees
2007-05-30 12:53               ` Mark Wielaard
2007-05-30 21:10                 ` Kris Van Hees
2007-06-01 15:27                   ` Andrew Cagney
2007-05-30 13:31               ` Andrew Cagney
2007-05-30 16:08               ` Andrew Cagney [this message]
2007-05-31  8:17                 ` Kris Van Hees
2007-05-31 18:05                   ` Mark Wielaard

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=465D7CC2.9080603@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).