error-reporting-tool.rst 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
  2. Using the Error Reporting Tool
  3. ******************************
  4. The error reporting tool allows you to submit errors encountered during
  5. builds to a central database. Outside of the build environment, you can
  6. use a web interface to browse errors, view statistics, and query for
  7. errors. The tool works using a client-server system where the client
  8. portion is integrated with the installed Yocto Project
  9. :term:`Source Directory` (e.g. ``poky``).
  10. The server receives the information collected and saves it in a
  11. database.
  12. There is a live instance of the error reporting server at
  13. https://errors.yoctoproject.org.
  14. When you want to get help with build failures, you can submit all of the
  15. information on the failure easily and then point to the URL in your bug
  16. report or send an email to the mailing list.
  17. .. note::
  18. If you send error reports to this server, the reports become publicly
  19. visible.
  20. Enabling and Using the Tool
  21. ===========================
  22. By default, the error reporting tool is disabled. You can enable it by
  23. inheriting the :ref:`ref-classes-report-error` class by adding the
  24. following statement to the end of your ``local.conf`` file in your
  25. :term:`Build Directory`::
  26. INHERIT += "report-error"
  27. By default, the error reporting feature stores information in
  28. ``${``\ :term:`LOG_DIR`\ ``}/error-report``.
  29. However, you can specify a directory to use by adding the following to
  30. your ``local.conf`` file::
  31. ERR_REPORT_DIR = "path"
  32. Enabling error
  33. reporting causes the build process to collect the errors and store them
  34. in a file as previously described. When the build system encounters an
  35. error, it includes a command as part of the console output. You can run
  36. the command to send the error file to the server. For example, the
  37. following command sends the errors to an upstream server::
  38. $ send-error-report /home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt
  39. In the previous example, the errors are sent to a public database
  40. available at https://errors.yoctoproject.org, which is used by the
  41. entire community. If you specify a particular server, you can send the
  42. errors to a different database. Use the following command for more
  43. information on available options::
  44. $ send-error-report --help
  45. When sending the error file, you are prompted to review the data being
  46. sent as well as to provide a name and optional email address. Once you
  47. satisfy these prompts, the command returns a link from the server that
  48. corresponds to your entry in the database. For example, here is a
  49. typical link: https://errors.yoctoproject.org/Errors/Details/9522/
  50. Following the link takes you to a web interface where you can browse,
  51. query the errors, and view statistics.
  52. Disabling the Tool
  53. ==================
  54. To disable the error reporting feature, simply remove or comment out the
  55. following statement from the end of your ``local.conf`` file in your
  56. :term:`Build Directory`::
  57. INHERIT += "report-error"
  58. Setting Up Your Own Error Reporting Server
  59. ==========================================
  60. If you want to set up your own error reporting server, you can obtain
  61. the code from the Git repository at :yocto_git:`/error-report-web/`.
  62. Instructions on how to set it up are in the README document.