public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Mark Wielaard <mark@klomp.org>
Cc: frysk@sourceware.org, Kris Van Hees <kris.van.hees@oracle.com>
Subject: Re: Automated build-and-test summary report (2007/06/18)
Date: Mon, 18 Jun 2007 13:45:00 -0000	[thread overview]
Message-ID: <20070618132257.GK17138@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1182170677.4534.35.camel@dijkstra.wildebeest.org>

On Mon, Jun 18, 2007 at 02:44:37PM +0200, Mark Wielaard wrote:
> Hi,
> (From the test-results list)
> 
> On Mon, 2007-06-18 at 05:35 -0700, Kris Van Hees wrote:
> > For more detailed results, please check out the reports at:
> > 
> >     http://build.alchar.org/~aedil/rep/
> >  [...]
> >   Old   -> New   Test
> >   -----    ----- ----------------------------------
> >   PASS  -> FAIL  frysk-core - testStepOver(frysk.rt.TestSteppingEngine)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferMapOverrun(frysk.proc.corefile.TestCorefileByteBuffer)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferPoke(frysk.proc.corefile.TestCorefileByteBuffer)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferPeek(frysk.proc.corefile.TestCorefileByteBuffer)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferPeekArray(frysk.proc.corefile.TestCorefileByteBuffer)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferMapUnderrun(frysk.proc.corefile.TestCorefileByteBuffer)
> >   FAIL  -> PASS  frysk-core - testSliceAddressSpace(frysk.proc.ptrace.TestByteBuffer)
> >   PASS  -> FAIL  frysk-core - testCoreFileByteBufferSequentialGet(frysk.proc.corefile.TestCorefileByteBuffer)
> 
> The core file tests did once fail for me with a pending SIGUSR1 during
> teardown. But I cannot replicate it now locally. It seems to be some
> kind of race during TestLib cleanup. Kris, are the full test results
> logs also available? I couldn't find them easily, and having the
> backtrace available would help with tracking these down.

Hm, I can see how easy it is to include links for the individual latest
builds to help with this.  In this case, if you click on the score (X /
Y number in the grid) for the specific host-package combination you get
the specific build result page.  It has a download link for the build
log in the upper right section of the page.

	Kris

  reply	other threads:[~2007-06-18 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070618123542.GJ17138@ca-server1.us.oracle.com>
2007-06-18 13:23 ` Mark Wielaard
2007-06-18 13:45   ` Kris Van Hees [this message]
2007-06-18 14:59     ` Mark Wielaard
2007-06-18 15:15       ` Kris Van Hees
2007-06-18 15:13   ` Phil Muldoon
2007-06-18 15:39     ` Kris Van Hees

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=20070618132257.GK17138@ca-server1.us.oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.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).