<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bb/ui/buildinfohelper.py, branch jethro-14.0.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=jethro-14.0.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=jethro-14.0.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2015-10-29T22:05:36+00:00</updated>
<entry>
<title>bitbake: toasterui: Create per-build logs</title>
<updated>2015-10-29T22:05:36+00:00</updated>
<author>
<name>Elliot Smith</name>
<email>elliot.smith@intel.com</email>
</author>
<published>2015-10-29T11:59:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a0791c19db7d5b33ce7a4e3614a574ad4a319a84'/>
<id>urn:sha1:a0791c19db7d5b33ce7a4e3614a574ad4a319a84</id>
<content type='text'>
Rather than relying on bug 8411, which is conveniently creating
separate log files for each of our builds, create our own
log file for each build.

The log files are created in the same tmp directories that
bitbake users, but are timestamped to the millisecond to avoid
name collisions.

Each log file is opened on a ParseStarted event (for builds
triggered by Toaster) or BuildStarted event (for builds on the
command line: Toaster doesn't get the ParseStarted event
for command-line builds).

The log file is closed on the BuildCompleted event, or if the
build fails.

Because we start logging on ParseStarted for Toaster builds,
we're able to capture the "Build Configuration" section which
bitbake writes to output.

[YOCTO #8373]

(Bitbake rev: 7974203cd8bc66dff1fcc55f8723dedefaf72840)

Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: add get_or_create_targets API</title>
<updated>2015-10-27T07:24:30+00:00</updated>
<author>
<name>Ed Bartosh</name>
<email>ed.bartosh@linux.intel.com</email>
</author>
<published>2015-10-16T17:31:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=851f0d82d9744e2eebb1f382a9963f3815b9822c'/>
<id>urn:sha1:851f0d82d9744e2eebb1f382a9963f3815b9822c</id>
<content type='text'>
Target objects are created before the build if build is
started from UI in build mode. However, in analysis mode Target
objects don't exist and need to be created using information
from bitbake events.

Added new API call get_or_create_targets to retrive existing
target objects or create them if they don't exist yet.

(Bitbake rev: ef69be31d133696bde54605f5a18da660099734c)

Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: Record critical errors</title>
<updated>2015-10-16T13:13:22+00:00</updated>
<author>
<name>Elliot Smith</name>
<email>elliot.smith@intel.com</email>
</author>
<published>2015-10-15T12:45:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=93f0b61749155ba600f38dff5604a68da548c486'/>
<id>urn:sha1:93f0b61749155ba600f38dff5604a68da548c486</id>
<content type='text'>
Critical errors (where a build failed for reasons of
misconfiguration, such as a machine being specified which is not
in a project's layers) were being ignored (only log records
up to ERROR level were being logged to Toaster's db). This meant that
the build would fail but would not correctly report why.

Add support for CRITICAL error levels to the LogMessage model,
include errors at this level in the errors property for a build,
and show errors at this level in the build dashboard.

[YOCTO #8320]

(Bitbake rev: b6eacbca9cacb607de864ab7d093deb296da8226)

Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Ed Bartosh &lt;ed.bartosh@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: buildinfohelper Detect command line builds</title>
<updated>2015-10-16T13:13:22+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-10-14T09:09:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ae82d778e67dc35a9a2a54d9893b0ae5f00bb197'/>
<id>urn:sha1:ae82d778e67dc35a9a2a54d9893b0ae5f00bb197</id>
<content type='text'>
When we're building using toaster as just a listener to bitbake
(analysis mode) we need to handle the case where the toaster configuration data
isn't present so we don't need to try and update the existing information.

(Bitbake rev: a22faae2c3a5948356ce3cbc73c34509de65d370)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: buildinfohelper Skip packages we have no build info about</title>
<updated>2015-10-11T04:39:04+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-10-07T13:55:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=41286f473086ef025d075bae1bb03a2929d1bfca'/>
<id>urn:sha1:41286f473086ef025d075bae1bb03a2929d1bfca</id>
<content type='text'>
If there are more packages listed as installed than we know about from
bitbake, and therefore have insufficient information to be able to
create a Toaster Package object then skip it. Also handle the case where
a dependency references such a package.

Also clarify the error logging.

(Bitbake rev: b4ce793685f70cab3f28cb4329aaaf3878cd62e8)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: buildinfohelper associate build data with built_recipe</title>
<updated>2015-10-11T04:39:03+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-10-07T13:55:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=97d000677eb3d28c7f88f93a0c3c5154c3df32ad'/>
<id>urn:sha1:97d000677eb3d28c7f88f93a0c3c5154c3df32ad</id>
<content type='text'>
Make sure we associate build data with the built recipe rather than
toaster's configuration copy of the recipe.

(Bitbake rev: 34d4ef7289d72d151ad0acdccab8b99c8c31221e)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: Revert "bitbake: toaster: don't re-create Target objects"</title>
<updated>2015-09-29T13:11:38+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-09-29T04:45:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fe29297c6a4e3096b0bdecde62a594a8e68f79c5'/>
<id>urn:sha1:fe29297c6a4e3096b0bdecde62a594a8e68f79c5</id>
<content type='text'>
This delete followed up the foreign keys and deleted things that were
not expected to be deleted.

This reverts commit 08000eb27eb8413686fb2c8daf14d234a8bff83a.

(Bitbake rev: 46b119eb62a5a612fe4c0847862d34f408e556f7)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: buildinfohelper Create a copy of the built layer and recipe</title>
<updated>2015-09-29T13:11:38+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-09-29T04:45:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e6d967dba254a9d2a53d8b5b9469ac6b672fb1b9'/>
<id>urn:sha1:e6d967dba254a9d2a53d8b5b9469ac6b672fb1b9</id>
<content type='text'>
Create a copy of the built layer and the recipes associated with it.
This is so that the user can view the historical information about a
build. i.e. a snapshot of the layer version and artifacts produced at
that build.

(Bitbake rev: 0683d9a2b15e3234a94437aaebac84bfcca1420b)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: Create a relationship between build information and toaster layers</title>
<updated>2015-09-29T13:11:38+00:00</updated>
<author>
<name>Michael Wood</name>
<email>michael.g.wood@intel.com</email>
</author>
<published>2015-09-29T04:45:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=922503f4c1d664edc5d3c0f66f262b3b4c3e5c56'/>
<id>urn:sha1:922503f4c1d664edc5d3c0f66f262b3b4c3e5c56</id>
<content type='text'>
Previously this layer relationship was done by trying to match path
information that came back to the buildinfohelper with trying to query for
data in toaster's layers table. This rarely matched due to the lose coupling.

(Bitbake rev: 838e77c7c3c4006abd1327343a004590ab652de9)

Signed-off-by: Michael Wood &lt;michael.g.wood@intel.com&gt;
Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: toaster: Add fake entry to Target_File for filesystem root</title>
<updated>2015-09-23T21:44:55+00:00</updated>
<author>
<name>Elliot Smith</name>
<email>elliot.smith@intel.com</email>
</author>
<published>2015-09-22T02:42:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=15b482b16b2340edc6f59a9c9e1d7f38bda9b6c2'/>
<id>urn:sha1:15b482b16b2340edc6f59a9c9e1d7f38bda9b6c2</id>
<content type='text'>
The files-in-image.txt file is produced by bitbake after an
image is created, listing all the files in the image.
However, this list doesn't include the root directory ('/').

buildinfohelper.py then tries to construct the filesystem
tree from this file, assuming that every directory apart from
the root directory (which is special-cased) can be assigned
a parent. But because the root directory isn't listed in
files-in-image.txt, an object for the root directory is never
created.

The direct subdirectories of the root ('./bin', './usr' etc.)
then can't be assigned a parent directory, as the object
representing the root directory doesn't exist. This
results in a Target_File lookup error and causes the
directory listing page to fail.

Fix this by creating a fake entry for the root directory
in the Target_File table, so that the direct subdirectories
of / can be assigned a parent. Note that it doesn't matter
that the root is faked, as its properties are never shown
in the directory structure tree.

[YOCTO #8280]

(Bitbake rev: a4015768183e5a3fa39a6c2b4dea0088ca182d80)

Signed-off-by: Elliot Smith &lt;elliot.smith@intel.com&gt;
Signed-off-by: brian avery &lt;avery.brian@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
