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/06/18)
Date: Mon, 18 Jun 2007 14:59:00 -0000 [thread overview]
Message-ID: <1182178578.4534.47.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20070618132257.GK17138@ca-server1.us.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Mon, 2007-06-18 at 06:22 -0700, Kris Van Hees wrote:
> 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.
It seems the build log only contains the harness output of setting up
the rpms, build infrastructure, running the testharness, but not the
actual make or make check output. Or am I looking for the wrong thing,
at the wrong place? Following your instructions I end up with:
http://build.alchar.org/~aedil/rep/coldstone/dl/frysk_dist.20070618-041627.log.bz2
In particular I would like to have the make check logs for the above new
FAILs in this message:
http://sourceware.org/ml/frysk-testresults/2007-q2/msg00017.html
What would be the URL for those?
Thanks,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-18 14:56 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
2007-06-18 14:59 ` Mark Wielaard [this message]
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=1182178578.4534.47.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).