summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-03-26 14:51:38 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-30 10:18:37 +0100
commitf1e9e335ee5f37a037522d5afa60249067432105 (patch)
tree10ec427ef464fa724c8d72f063d11d28a0c339f5 /documentation/dev-manual
parentaa73618df5474f1c51c0c37a32831d04e8435cc9 (diff)
downloadpoky-f1e9e335ee5f37a037522d5afa60249067432105.tar.gz
dev-manual, ref-manual: Added error reporting tool information
Fixes [YOCTO #1562] In the dev-manual, I created a new section called "Using the Error Reporting Tool" that describes how to use this feature. The text was based on information I received from Andreea Proca. In the ref-manual, I added a new variable entry for ERR_REPORT_DIR in the glossary and a new report-error class in the class chapter. (From yocto-docs rev: 70a5538fefcc1b77958fe4b2f29be00354f4137a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml67
1 files changed, 67 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 5dced8b608..c11df717d3 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -6988,6 +6988,73 @@
6988 </para> 6988 </para>
6989 </section> 6989 </section>
6990 </section> 6990 </section>
6991
6992 <section id='using-the-error-reporting-tool'>
6993 <title>Using the Error Reporting Tool</title>
6994
6995 <para>
6996 The error reporting tool allows you to
6997 submit errors encountered during builds to a central database.
6998 Outside of the build environment, you can use a web interface to
6999 browse errors, view statistics, and query for errors.
7000 The tool works using a client-server system where the client
7001 portion is integrated with the installed Yocto Project
7002 <link linkend='source-directory'>Source Directory</link>
7003 (e.g. <filename>poky</filename>).
7004 The server receives the information collected and saves it in a
7005 database.
7006 </para>
7007
7008 <para>
7009 By default, the error reporting tool is disabled.
7010 You can enable it by inheriting the
7011 <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-report-error'><filename>report-error</filename></ulink>
7012 class by adding the following statement to the end of
7013 your <filename>local.conf</filename> file in your
7014 <link linkend='build-directory'>Build Directory</link>.
7015 <literallayout class='monospaced'>
7016 INHERIT += "report-error"
7017 </literallayout>
7018 To disable the feature, simply remove or comment out the statement.
7019 </para>
7020
7021 <para>
7022 By default, the error reporting feature stores information in
7023 <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-LOG_DIR'><filename>LOG_DIR</filename></ulink><filename>}/error-report</filename>.
7024 However, you can specify a directory to use by adding the following
7025 to your <filename>local.conf</filename> file:
7026 <literallayout class='monospaced'>
7027 ERR_REPORT_DIR = "path"
7028 </literallayout>
7029 Enabling error reporting causes the build process to collect
7030 the errors and store them in a file as previously described.
7031 When the build system encounters an error, it includes a command
7032 as part of the console output.
7033 You can run the command to send the error file to the server.
7034 For example, the following command sends the errors to an upstream
7035 server:
7036 <literallayout class='monospaced'>
7037 send-error-report /home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt [server]
7038 </literallayout>
7039 In the above example, the <filename>server</filename> parameter is
7040 optional.
7041 By default, the errors are sent to a database used by the entire
7042 community.
7043 If you specify a particular server, you can send them to a different
7044 database.
7045 </para>
7046
7047 <para>
7048 When sending the error file, you receive a link that corresponds
7049 to your entry in the database.
7050 For example, here is a typical link:
7051 <literallayout class='monospaced'>
7052 http://localhost:8000/Errors/Search/1/158
7053 </literallayout>
7054 Following the link takes you to a web interface where you can
7055 browse, query the errors, and view statistics.
7056 </para>
7057 </section>
6991</chapter> 7058</chapter>
6992 7059
6993<!-- 7060<!--