[bitbake-devel,0/2] improve recovery when something goes horribly wrong

Submitted by Peter Seebach on Nov. 20, 2013, 12:31 a.m.


Message ID cover.1384907121.git.peter.seebach@windriver.com
State New
Headers show


git://git.yoctoproject.org/poky-contrib seebs/warning_helper

Commit Message

Peter Seebach Nov. 20, 2013, 12:31 a.m.
Certain early failures can result in things going wrong in ways that
prevent "bitbake -e" from running, creating strange or cryptic failures,
and even when they're not all that cryptic, lack of include tracking
or variable history tracking can be a significant disadvantage.

These patches address one of the failure modes, and make it possible for
an oe-core change to address another.

The first patch makes run.* scripts work even when the path name generated
contains unexpanded variable names, by quoting the argument to cd. The
second provides an isTracking() to DataSmart to allow the sanity checks
to be normal errors rather than fatal errors when trying to run with
tracking enabled (which only occurs when you want to dump the results of
the tracking).

The following changes since commit a66ee0994645aa5658b2f5ea134ed17d89f8751a:

  fetch2: Fix handling of SCM mirrors in MIRRORS (2013-11-19 13:22:10 +0000)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib seebs/warning_helper

Peter Seebach (2):
  build.py: add single-quotes around already-expanded directory name
  data_smart.py: Add isTracking() to datasmart

 lib/bb/build.py      |    2 +-
 lib/bb/data_smart.py |    3 +++
 2 files changed, 4 insertions(+), 1 deletions(-)