public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Automated build-and-test summary report (2007/11/05)
Date: Tue, 06 Nov 2007 12:23:00 -0000	[thread overview]
Message-ID: <1194351776.3855.31.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20071106114115.GD10486@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

Hi Kris,

On Tue, 2007-11-06 at 06:41 -0500, Kris Van Hees wrote:
> Well, the build report is definitely at the mentioned URL (just verified that)
> although it might seem like it is missing information.  I.e. the build status
> ends with the checksum phase.  That is a typical situation where no changes
> were found between the previous source tree and the current one.  If it seems
> confusing, I'll make changes to the reporting to make that more clear.

OK, so "First failure:  no changes - not built" actually means that the
sources didn't change from the last time the builder ran and so it
wasn't build. Correct? If so the "First Failure" part confused me.

> The fact that the (usually) downloadable logs are not being shown as links
> (that section is empty) is a bug.  I'll send notice when it is resolved.

OK, yes, that was the other confusion.

Thanks,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-11-06 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071105140036.GA2015@oracle.com>
2007-11-06 10:25 ` Mark Wielaard
2007-11-06 11:42   ` Kris Van Hees
2007-11-06 12:23     ` Mark Wielaard [this message]
2007-11-06 13:45       ` Kris Van Hees
2007-11-06 15:03         ` 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=1194351776.3855.31.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=frysk@sourceware.org \
    --cc=kris.van.hees@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).