<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/buildman/control.py, branch v2015.01-rc2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/control.py?h=v2015.01-rc2</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/control.py?h=v2015.01-rc2'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2014-09-21T18:03:07Z</updated>
<entry>
<title>buildman: Fix the logic for the bloat command</title>
<updated>2014-09-21T18:03:07Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-15T02:23:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7798e2285fda17aa2268cbe18498678cf857905f'/>
<id>urn:sha1:7798e2285fda17aa2268cbe18498678cf857905f</id>
<content type='text'>
This check should now be done whatever mode buildman is running in, since
we may be displaying information while building.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Ignore conflicting tags</title>
<updated>2014-09-09T22:38:31Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=950a23133d8235778ea29f5d9587edec7d9bbc0a'/>
<id>urn:sha1:950a23133d8235778ea29f5d9587edec7d9bbc0a</id>
<content type='text'>
Tags like Series-version are normally expected to appear once, and with a
unique value. But buildman doesn't actually look at these tags. So ignore
conflicts.

This allows bulidman to build a branch containing multiple patman series.

Reported-by: Steve Rae &lt;srae@broadcom.com&gt;
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Permit branch names with an embedded '/'</title>
<updated>2014-09-09T22:38:31Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f7582ce8496f19edf845d1f62c4b7f385e4cd864'/>
<id>urn:sha1:f7582ce8496f19edf845d1f62c4b7f385e4cd864</id>
<content type='text'>
At present buildman naively uses the branch name as part of its directory
path, which causes problems if the name has an embedded '/'.

Replace these with '_' to fix the problem.

Reported-by: Steve Rae &lt;srae@broadcom.com&gt;
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Provide an internal option to clean the outpur dir</title>
<updated>2014-09-09T22:38:29Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=883a321a4bee2d2b2f16e445060c17494e76bc48'/>
<id>urn:sha1:883a321a4bee2d2b2f16e445060c17494e76bc48</id>
<content type='text'>
For testing it is useful to clean the output directory before running a
test. This avoids a test interfering with the results of a subsequent
test by leaving data around.

Add this feature as an optional parameter to the control logic.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Allow tests to have their own boards</title>
<updated>2014-09-09T22:38:29Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=823e60b62a98061a662536093d46f8f26f6d318f'/>
<id>urn:sha1:823e60b62a98061a662536093d46f8f26f6d318f</id>
<content type='text'>
Rather than reading boards.cfg, which may take time to generate and is not
necessarily suitable for running tests, create our own list of boards.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Set up bsettings outside the control module</title>
<updated>2014-09-09T22:38:28Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fd03d63f347e28e4e4394245210f048c82c9b085'/>
<id>urn:sha1:fd03d63f347e28e4e4394245210f048c82c9b085</id>
<content type='text'>
Move the bsettings code back to the main buildman.py file, so we can do
something different when testing.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add a functional test</title>
<updated>2014-09-09T22:38:28Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d4144e45b4245c60f50d456293cad2f53373efcd'/>
<id>urn:sha1:d4144e45b4245c60f50d456293cad2f53373efcd</id>
<content type='text'>
Buildman currently lacks testing in many areas, including its use of git,
make and many command-line flags.

Add a functional test which covers some of these areas. So far it does
a fake 'build' of all boards for the current source tree.

This version reads the real ~/.buildman and boards.cfg files. Future work
will improve this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Move full help code into the control module</title>
<updated>2014-09-09T22:38:27Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-09-06T01:00:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=48ba5856eb47dca0abc4d24e7c4e3ce1fd2628f1'/>
<id>urn:sha1:48ba5856eb47dca0abc4d24e7c4e3ce1fd2628f1</id>
<content type='text'>
There is no good reason to keep this code separate. Move it into control.py
so it is easier to test.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add an option to show which boards caused which errors</title>
<updated>2014-09-05T19:40:43Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-08-28T15:43:43Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ed9666573eb08b4d8f18855d9f62e22ba0316ee9'/>
<id>urn:sha1:ed9666573eb08b4d8f18855d9f62e22ba0316ee9</id>
<content type='text'>
Add a -l option to display a list of offending boards against each
error/warning line. The information will be shown in brackets as below:

02: wip
   sandbox: +   sandbox
       arm: +   seaboard
+(sandbox) arch/sandbox/cpu/cpu.c: In function 'timer_get_us':
+(sandbox) arch/sandbox/cpu/cpu.c:40:9: warning: unused variable 'i' [-Wunused-variable]
+(seaboard) board/nvidia/seaboard/seaboard.c: In function 'pin_mux_mmc':
+(seaboard) board/nvidia/seaboard/seaboard.c:36:9: warning: unused variable 'fred' [-Wunused-variable]
+(seaboard)      int fred;
+(seaboard)          ^

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Implement an option to exclude boards from the build</title>
<updated>2014-09-05T19:40:43Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2014-08-28T15:43:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3cf4ae6f8672cd10ddba4b18bf82e4d03aeb15e6'/>
<id>urn:sha1:3cf4ae6f8672cd10ddba4b18bf82e4d03aeb15e6</id>
<content type='text'>
Some boards are known to be broken and it is convenient to be able to
exclude them from the build.

Add an --exclude option to specific boards to exclude. This uses the
same matching rules as the normal 'include' arguments, and is a comma-
separated list of regular expressions.

Suggested-by: York Sun &lt;yorksun@freescale.com&gt;
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
