Bug 9884

Summary:	Better configuration on whether toaster event files are written or not
Product:	[Infrastructure] AutoBuilder	Reporter:	Joshua Lock <joshuagloe>
Component:	autobuilder	Assignee:	Bill Randle <bill.randle>
Status:	RESOLVED FIXED	QA Contact:	Libertad <libertad.gonzalez.de.la.cruz>
Severity:	normal
Priority:	High	CC:	infras.ab.watcher, Infras.watcher, jku, jose.perez.carranza, pidge, sgw
Version:	2.2
Target Milestone:	2.2 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 Joshua Lock 2016-07-06 15:36:41 UTC

We have observed bitbake_eventlog.json being generated in unexpected places during autobuilder builds.

* document when we expect event logs to be generated
* ensure the current code only generates event logs when we expect them to
* make generation of event logs more readily configurable — both when and where

Comment 1 Bill Randle 2016-07-06 17:37:09 UTC

When the event log is needed, it needs to go elsewhere than the top level build directory.

Need to also allow enabling or disabling of toaster build logging globally.

A suggested default is for toaster build logging be "off" for now. We
may choose to enable it at some point.

Comment 2 Joshua Lock 2016-07-13 21:29:01 UTC

*** Bug 8230 has been marked as a duplicate of this bug. ***

Comment 3 Bill Randle 2016-07-14 17:09:26 UTC

The patches (1) make generation of the eventlog optional, by having a user selection in the Forced Build web pages, (2) places the eventlog in build/tmp/log, instead of build and (3) adds a timestamp to the eventlog filename since multiple event logs can be generated during a multi-image buildset and otherwise only the last one would otherwise be saved.

Patch set sent to yocto mailing list.

Comment 4 Bill Randle 2016-07-19 15:50:39 UTC

Merged to master on 7/19/16 by Beth.