documentation/dev-manual/debugging.rst

31 -  ":ref:`dev-manual/debugging:viewing logs from failed tasks`" describes
32    how to find and view logs from tasks that failed during the build
44 -  ":ref:`dev-manual/debugging:viewing dependencies between recipes and tasks`"
53 -  ":ref:`dev-manual/debugging:running specific tasks`" describes
55    to run specific tasks in the build chain. It can be useful to run
56    tasks "out-of-order" when trying isolate build issues.
86 Viewing Logs from Failed Tasks
92 :ref:`ref-tasks-compile` task of the
136    will not be visible to other tasks.
155    system (including the behavior of the :ref:`ref-manual/tasks:normal recipe build tasks`) is
194       :ref:`ref-tasks-package` task
219 Viewing Dependencies Between Recipes and Tasks
240 -  ``task-depends.dot``: A graph showing dependencies between tasks.
261       :ref:`ref-tasks-configure`
263       :ref:`ref-tasks-populate_sysroot`
311    :ref:`ref-tasks-fetch` task of the
317    For tasks that are accelerated through the shared state
356 information without executing tasks by using either of the following
371    tasks need to be re-run in situations where that is not expected.
398 rebuilding tasks. Collectively, this scheme is known as "shared state
423 invalidate the cache and force the tasks to run. The steps you can take
427 :ref:`ref-tasks-package` or the
438 Running Specific Tasks
441 Any given recipe consists of a set of tasks. The standard BitBake
442 behavior in most cases is: :ref:`ref-tasks-fetch`, :ref:`ref-tasks-unpack`, :ref:`ref-tasks-patch`,
443 :ref:`ref-tasks-configure`, :ref:`ref-tasks-compile`, :ref:`ref-tasks-install`, :ref:`ref-tasks-pac…
444 :ref:`do_package_write_* <ref-tasks-package_write_deb>`, and :ref:`ref-tasks-build`. The default ta…
445 :ref:`ref-tasks-build` and any tasks on which it depends build first. Some tasks,
446 such as :ref:`ref-tasks-devshell`, are not part of the default build chain. If you
453 tasks (including tasks from other recipes) that the specified task
457 ":ref:`overview-manual/concepts:stamp files and the rerunning of tasks`"
469    :ref:`ref-tasks-devshell` task is because the
485 last command reruns all tasks (basically the packaging tasks) after the
486 compile. BitBake recognizes that the :ref:`ref-tasks-compile` task was rerun and
487 therefore understands that the other tasks also need to be run again.
490 :ref:`ref-manual/tasks:normal recipe build tasks`
499 :ref:`ref-tasks-build` task, which is
500 the default task if no task is given, and the tasks on which it depends.
508 causes the task and its dependent tasks to be rerun through the normal
513    BitBake explicitly keeps track of which tasks have been tainted in
515    builds involving such tasks:
532 You can view a list of tasks in a given package by running the
533 :ref:`ref-tasks-listtasks` task as follows::
623 a function that determines the number of tasks needed to be run. See the
624 ":ref:`ref-tasks-listtasks`"
630            bb.note("There are 47 tasks to run")
638        bb.plain("The tasks present are abc")