* so ... what's the proper way to report a build failure?
@ 2010-06-29 14:08 Robert P. J. Day
2010-06-29 15:04 ` John Willis
0 siblings, 1 reply; 5+ messages in thread
From: Robert P. J. Day @ 2010-06-29 14:08 UTC (permalink / raw)
To: OpenEmbedded Development mailing list
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?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Top-notch, inexpensive online Linux/OSS/kernel courses
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: so ... what's the proper way to report a build failure?
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
2010-06-29 15:52 ` J. L.
0 siblings, 1 reply; 5+ messages in thread
From: John Willis @ 2010-06-29 15:04 UTC (permalink / raw)
To: openembedded-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: so ... what's the proper way to report a build failure?
2010-06-29 15:04 ` John Willis
@ 2010-06-29 15:52 ` J. L.
2010-06-29 17:09 ` John Willis
0 siblings, 1 reply; 5+ messages in thread
From: J. L. @ 2010-06-29 15:52 UTC (permalink / raw)
To: openembedded-devel
The wiki link for me had nothing on it, I have been wondering the same
things myself.
On Tue, Jun 29, 2010 at 8:04 AM, John Willis
<John.Willis@distant-earth.com>wrote:
> 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<http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg02%0A876.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
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-06-29 17:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-06-29 15:52 ` J. L.
2010-06-29 17:09 ` John Willis
2010-06-29 17:14 ` J. L.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.