summaryrefslogtreecommitdiffstats
path: root/meta/classes/report-error.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* report-error.bbclass: Added file syncronization.Mariano Lopez2015-07-081-1/+10
| | | | | | | | | | | | | | | errorreport_handler would fail if several errors are triggered at the same time because of two proccess writting to the same file. This patch add the required syncronization to handle concurrent process. [YP #7899] (From OE-Core rev: c7bff5e7fdd2cbf6f22bfe9a74ceb6e19ef3b5d8) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error: Update information on the submission processMichael Wood2015-03-101-2/+2
| | | | | | | | | | | The new send-error-report will prompt for review of items and the server is now specified by using the -s argument. (From OE-Core rev: c195d70f35ea522854dcdd53aeae60eec6b7ad7e) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error: Catch un-readable log dataMichael Wood2015-02-031-3/+7
| | | | | | | | | | | If a log data cannot be decoded to utf-8 or read then handle this gracefully. This can happen if a log file contains binary or something goes wrong with the file open process. (From OE-Core rev: 787ffc5e12f1639aa5e0917bb23deced53a0478e) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error: Handle the case no logfile existsRichard Purdie2014-12-211-3/+6
| | | | | | | | | If the task fails early, no error log may exist. Currently we crash in that case, this handles the situation more gracefully. (From OE-Core rev: 1e6bfcab47f532677f87683ba2f5e5fb905e9ba5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/report-error: tweak summary messagePaul Eggleton2014-06-291-2/+2
| | | | | | | | | | | | * We don't want everyone to remove their identifying info, just if they feel the need to * Split lines for clarity * A couple of grammar/spelling tweaks (From OE-Core rev: b5c7538416e4c7a9e594edf930fa7ee844a347e6) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error: Add posting in the public noteSaul Wold2014-04-241-0/+1
| | | | | | | (From OE-Core rev: c2eb5cd1aa4632f7ee8c261414e599dcb6f40a8b) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* report-error.bbclass: new class to save build information when errors occurAndreea Proca2014-02-141-0/+66
Class is used to save data about errors after every task that failed. Errors saved as json files in ERROR_REPORT_DIR (defaults to tmp/log/error-report). To use this class one has to add INHERIT += "report-error" to local.conf. scripts/send-error-report is a simple script that sends the json file to a HTTP server that collects data (git://git.yoctoproject.org/error-report-web is a Django web interface that can be used to receive and visualize the error reports). The script will give you an URL where you can find your report. (From OE-Core rev: f186b4c7c6c975638e60b30a512d669dc6dc390f) Signed-off-by: Andreea Proca <andreea.b.proca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OpenPOWER on IntegriCloud