<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 22, 2015 at 7:57 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1c2" class="a3s" style="overflow:hidden">Looking at and thinking about:<br>
<br>
<a href="https://bugzilla.yoctoproject.org/show_bug.cgi?id=5187" target="_blank">https://bugzilla.yoctoproject.org/show_bug.cgi?id=5187</a><br>
<br>
We have several issues. Firstly, DATE and TIME are locked in stone when<br>
the base configuration is parsed. This may cause images to overwrite<br>
previous versions for example if DATE and TIME are not re-evaluated. We<br>
could fix this by specifically setting DATE and TIME in bitbake at<br>
BuildStart?<br></div></blockquote><div><br></div><div>Seems quite reasonable to me. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1c2" class="a3s" style="overflow:hidden">
Secondly, there is one cooker log file opened for the duration of the<br>
cooker lifecycle. This is a cooker log, not a log of each build so that<br>
is perhaps not surprising (and is the core problem in the above bug).<br>
There is no overwriting of the log file, it just keeps growing with each<br>
build.<br>
<br>
We could trigger knotty to write out build specific log files based on<br>
the BuildStart/Finish events?</div></blockquote><div><br></div><div>This doesn't seem unreasonable, though a build isn't necessarily bound to a particular UI, is it? Should that go into the server or perhaps the ui helper at least? Hmm.</div></div>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>