Event Logger Data Interfaces

Documenting the event logger data interfaces and action models. The EVT is the EVent Tra

EVT

Bitbake uses a push-event model where it sends pickled Python objects over XMLRPC to an event sink.

interface with bitbake

The bitbake server runs at IP:PORT location. A event server controller lives at IP:(PORT+2) accepting a XMLRPC interface with two commands: registerEventHandler and unregisterEventHandler.

EVT will run resident in memory, connecting to the bitbake server and accepting events. It will have an internal state that will follow the internal state of the bitbake server. This allows the EVT to infer information about the server state, and export this information to the DSI.

The event list that it receives from Bitbake is documented here:

Event object type	action taken in Knotty	action in EVT
bb.runqueue.runQueueExitWait
bb.event.LogExecTTY
logging.LogRecord
bb.build.TaskFailed
bb.build.TaskBase
bb.event.ParseStarted
bb.event.ParseProgress
bb.event.ParseCompleted
bb.event.CacheLoadStarted
bb.event.CacheLoadProgress
bb.event.CacheLoadCompleted
bb.command.CommandFailed
bb.command.CommandExit
bb.command.CommandCompleted
bb.cooker.CookerExit
bb.event.MultipleProviders
bb.event.NoProvider
bb.runqueue.sceneQueueTaskStarted
bb.runqueue.runQueueTaskStarted
bb.runqueue.runQueueTaskFailed
bb.runqueue.sceneQueueTaskFailed
bb.event.BuildBase	ignored	ignored
bb.event.StampUpdate	ignored	ignored
bb.event.ConfigParsed	ignored	timestamp entry
bb.event.RecipeParsed	ignored	timestamp entry
bb.event.RecipePreFinalise	ignored	ignored
bb.runqueue.runQueueEvent	ignored
bb.runqueue.runQueueExitWait	ignored
bb.event.OperationStarted	ignored	timestamp
bb.event.OperationCompleted	ignored	timestamp, operation complete, timing
bb.event.OperationProgress	ignored	ignored
bb.event.DiskFull	ignored	error