Skip to content

improve recovery when something goes horribly wrong

Peter Seebach bitbake-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2build.py: add single-quotes around already-expanded directory namelib/bb/build.py+1 -10 replies
2/2data_smart.py: Add isTracking() to datasmartlib/bb/data_smart.py+3 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] improve recovery when something goes horribly wrong

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
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=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(-)