On 14/06/16 00:32, Aníbal Limón wrote:
In order to support other errors not only Recipe ones adds
a ERROR_TYPE field to the Build model defaults to "Recipe".
Add a class for store BuildErrorType currently supported
Recipe, Core, Bitbake selftest and OE selftest.
[YOCTO #7583]
Signed-off-by:
Fix link so that we don't perform a full text search for the
SHA/revision and just filter for it using the commit field. This should
drastically reduce page loading time on the error reporting site.
[YOCTO #9295]
Signed-off-by: Michael Wood <michael.g.w...@intel.com>
---
.../buildbot/stat
On 30/09/15 14:54, mariano.lo...@linux.intel.com wrote:
From: Mariano Lopez
If the server receives a error log with Unicode
character in it, it will throw and internal server
error, this is caused because the server doesn't
try to convert everything to ASCII
I've recently added a feature which was requested for the
error-report-web project[1] to add some kind of error matching
mechanism, this is now live on http://errors.yoctoproject.org
I'd be interested to hear If anyone has feedback regarding the similar
errors matching, whether it's useful or
Hi,
I've updated the errors.yoctoproject.org site with the latest version of
error-report-web [1] that myself and Belén have been working on.
error-report-web is a project to provide a web service that can be used
to collect and display build error reports. Error report generation can
be
Before we commit the error report metadata to the database do a
rudimentary check on all fields that are passed to the graphs page to
avoid any XSS happening.
Signed-off-by: Michael Wood michael.g.w...@intel.com
---
Post/parser.py | 13 +
1 file changed, 13 insertions(+)
diff --git