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.
Hello I am assigning it to Andreea Proca.
*** Bug 3361 has been marked as a duplicate of this bug. ***
I will set it to resolved. The web interface can be found here: http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/
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
Scott: Your assumption is correct, the build finishes and the user then decides what to do with any errors.
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.
Andreea Proca gave the changes a review and had no comments. I am resetting the documentation flag to "Done.". Scott
Marked as Verified.