Bug 1562

Summary:	kernel oops style error collection server
Product:	[Build System, Metadata & Runtime] Meta-yocto	Reporter:	Richard Purdie <richard.purdie>
Component:	meta-yocto	Assignee:	Andreea Brandusa Proca <andreea.b.proca>
Status:	VERIFIED FIXED	QA Contact:
Severity:	enhancement
Priority:	High	CC:	bluelightning, jessica.zhang, laurentiu.serban, mark.hatle, poky.bs.watcher, poky.watcher, sgw, srifenbark, sstncr
Version:	unspecified
Target Milestone:	1.6
Hardware:	x86
OS:	Multiple
Whiteboard:	28 March 2014: Setting documentation flag to "Done."
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Done (doc changes complete)
Bug Depends on:
Bug Blocks:	4682

Description Richard Purdie 2011-10-03 07:19:08 UTC

In a similar way to how kerneloops.org operated, it would be great to have an online servicer people could submit build failures to. This would collect up all the appropriate debug information and be a service people could share error information with. It would improve things for a user by:

a) Allow submitting all needed error information in one go (host OS, the error logs, version of the metadata, key variables such as MACHINE)

b) Allow statistical tracking of the errors people were seeing so the more common ones could be prioritized for fixing.

For security and data protection reasons, the service would be opt in and not enabled by default.

Comment 1 Laurentiu Serban 2012-12-06 13:14:25 UTC

Hello I am assigning it to Andreea Proca.

Comment 2 Richard Purdie 2013-04-24 15:32:43 UTC

*** Bug 3361 has been marked as a duplicate of this bug. ***

Comment 3 Andreea Brandusa Proca 2014-02-12 13:44:27 UTC

I will set it to resolved. 
The web interface can be found here: http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/

Comment 4 Scott Rifenbark 2014-03-26 20:47:02 UTC

Hi, 

Based on the excellent material that Andreea provided, I have added three new areas to the docs to address the documentation portion of this fix.  I need some review of the areas:

http://www.yoctoproject.org/dev-manual/dev-manual.html#using-the-error-reporting-tool - This is the main usage section on the tool.

http://www.yoctoproject.org/ref-manual/ref-manual.html#ref-classes-report-error - This is the new entry for the report-error class.

http://www.yoctoproject.org/ref-manual/ref-manual.html#var-ERR_REPORT_DIR - this is the new variable entry for ERR_REPORT_DIR.

Let me know of any changes or corrections. One thing I was unsure of is the flow for using this.  Does the build chug along and any errors are reported along with the command?  This would mean the user must wait for the build to complete and then examine the build console log or output to find the commands to ultimately send off.  Or, does the build interactively stop on an error and allow you send a command?  I assumed it would finish the build and then it would be up to the user to find the error messages and send the commands outside the build operation.

Thanks 
Scott

Comment 5 Richard Purdie 2014-03-26 21:07:05 UTC

Scott: Your assumption is correct, the build finishes and the user then decides what to do with any errors.

Comment 6 Scott Rifenbark 2014-03-27 15:05:26 UTC

Sorry about the links to the docs... I left out part of the URL.  Here are the correct links.


http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#using-the-error-reporting-tool - This is the main usage section on the tool.

http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#ref-classes-report-error - This is the new entry for the report-error class.

http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#var-ERR_REPORT_DIR - this is the new variable entry for ERR_REPORT_DIR.

Comment 7 Scott Rifenbark 2014-03-28 12:00:08 UTC

Andreea Proca gave the changes a review and had no comments.  I am resetting the documentation flag to "Done.".

Scott

Comment 8 Stefan Stanacar 2014-04-01 09:01:23 UTC

Marked as Verified.