[bitbake-devel,1/4] cookerdata: fix variable history not showing in bitbake -e with memres

Submitted by Paul Eggleton on June 9, 2017, 1:34 p.m. | Patch ID: 140656


Message ID 0d1c9d13726e3a56367fa46c148b56f7cda9c5eb.1497014984.git.paul.eggleton@linux.intel.com
State New
Headers show

Commit Message

Paul Eggleton June 9, 2017, 1:34 p.m.
CookerConfiguration sets the "tracking" option to True when -e is
specified in order to have history tracking enabled in the datastore
so that we can show variable history (which isn't enabled by default for
performance reasons), however in memory resident mode this wasn't doing
anything because it was happening on the UI side only. We do have a
mechanism for updating the cooker configuration in the server, but the
tracking option wasn't being included in the list of options we updated,
so we just need to add this option to fix the issue.

Fixes [YOCTO #10730].

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
 lib/bb/cookerdata.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch hide | download patch | download mbox

diff --git a/lib/bb/cookerdata.py b/lib/bb/cookerdata.py
index 722d860..6b850d3 100644
--- a/lib/bb/cookerdata.py
+++ b/lib/bb/cookerdata.py
@@ -76,7 +76,7 @@  class ConfigParameters(object):
         for o in ["abort", "tryaltconfigs", "force", "invalidate_stamp", 
                   "verbose", "debug", "dry_run", "dump_signatures", 
                   "debug_domains", "extra_assume_provided", "profile",
-                  "prefile", "postfile"]:
+                  "prefile", "postfile", "tracking"]:
             options[o] = getattr(self.options, o)
         ret, error = server.runCommand(["updateConfig", options, environment])