Bug 10741

Summary: memres: heartbeat and disk monitoring needs further testing
Product: [Build System, Metadata & Runtime] BitBake Reporter: Patrick Ohly <patrick.ohly>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: poky.bs.watcher, poky.watcher, randy.macleod
Version: unspecified   
Target Milestone: 2.4 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Patrick Ohly 2016-11-29 16:46:39 UTC 
While testing the bitbake and OE-core "system statistics sampling" patches, some oddities were observed which will have to be re-tested once memres is considered more stable.

1. Add BB_HEARTBEAT_EVENT="foo" to local.conf, run a build. ProcessServer.run() should print a warning about "Ignoring invalid BB_HEARTBEAT_EVENT" but that wasn't visible anywhere (neither console nor log file).

2. INHERIT += "buildstats", run a build. Check tmp/buildstats/*/monitor_disk.log. It should be non-empty, but was when using memres bitbake. This implies that bb.event.HeartbeatEvent and/or bb.event.MonitorDiskEvent were not getting emitted.
Comment 1 Richard Purdie 2017-07-07 14:03:10 UTC 
These issues are both because memres bitbake uses server/xmlrpc.py and Patrick only added Heartbeat code to server/process.py.