From: "John Willis" <John.Willis@Distant-earth.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: so ... what's the proper way to report a build failure?
Date: Tue, 29 Jun 2010 16:04:14 +0100 [thread overview]
Message-ID: <01fb01cb179c$580068f0$08013ad0$@Distant-earth.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006291005050.10428@lynx>
Hi Robert,
> given that i like to keep up with the OE dev branch and test build a
> beagleboard-demo-image as necessary, what is the *encouraged* way to
> report a new build failure? on the OE list? on the angstrom list?
> tinderbox?
>
> after a "git pull" earlier this morning, "realpath-1.15" fails to build.
what
> should i do with the error diagnostics?
Pretty sure this has been suggested in the past ;-)
(http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg02
876.html) but I'll say again, setting up Tinderbox
(http://tinderbox.openembedded.net/) has to be a pretty good starting place
to collaborate on build issues.
It's really easy to setup
(http://wiki.openembedded.net/index.php/How_do_I_send_automatic_success_and_
failure_reports) and the classes will automatically deal with uploading of
your fail logs/build info etc. so you can refer others to it (and for that
matter, see if others are building the same packages without issue).
Regards,
John
next prev parent reply other threads:[~2010-06-29 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 14:08 so ... what's the proper way to report a build failure? Robert P. J. Day
2010-06-29 15:04 ` John Willis [this message]
2010-06-29 15:52 ` J. L.
2010-06-29 17:09 ` John Willis
2010-06-29 17:14 ` J. L.
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='01fb01cb179c$580068f0$08013ad0$@Distant-earth.com' \
--to=john.willis@distant-earth.com \
--cc=openembedded-devel@lists.openembedded.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