<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/buildman/builderthread.py, branch v2025.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/builderthread.py?h=v2025.07</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/builderthread.py?h=v2025.07'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2025-03-04T19:32:15Z</updated>
<entry>
<title>Merge patch series "tools: Minor clean-ups for the command library"</title>
<updated>2025-03-04T19:32:15Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2025-03-04T19:31:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=986ab810fa2cb095f5617349baa5c88d83cffc46'/>
<id>urn:sha1:986ab810fa2cb095f5617349baa5c88d83cffc46</id>
<content type='text'>
Simon Glass &lt;sjg@chromium.org&gt; says:

This series adds comments and fixes pylint warnings in the command
library. It also introduces a new, simpler way of running a single
command.

Link: https://lore.kernel.org/r/20250203162704.627469-1-sjg@chromium.org
</content>
</entry>
<entry>
<title>u_boot_pylib: Add a function to run a single command</title>
<updated>2025-03-04T19:31:49Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2025-02-03T16:26:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3d094ce28a22690c3d672988af5f161310822603'/>
<id>urn:sha1:3d094ce28a22690c3d672988af5f161310822603</id>
<content type='text'>
Add a helper to avoid needing to use a list within a list for this
simple case.

Update existing users of runpipe() to use this where possible.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>u_boot_pylib: Move gitutil into the library</title>
<updated>2025-02-17T17:17:55Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2025-02-09T21:26:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5c33fb028865bdc490aa0db2980987149786b00f'/>
<id>urn:sha1:5c33fb028865bdc490aa0db2980987149786b00f</id>
<content type='text'>
Move this file into U-Boot's Python library, so that it is no-longer
part of patman.

This makes a start on:

https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/35

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Record an error if a toolchain is missing</title>
<updated>2025-01-25T22:27:24Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-12-14T18:20:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bd7883f3467645359f72647f78abffbdd5a236fa'/>
<id>urn:sha1:bd7883f3467645359f72647f78abffbdd5a236fa</id>
<content type='text'>
Buildman has always treated the lack of a toolchain as an infrastructure
problem rather than a build failure.

However the logic for this is not correct, since it does not write a
'done' file in this case.

As a result, one of two things can happen.

1. If a previous build ran in the same (output) directory, the outcome
   of *that* build is recorded as the outcome of this one
2. Otherwise, no outcome is recorded

Obviously this inconsistency is not ideal. While (2) is rare, it can be
very confusing as the build sort-of fails but does not produce any
summary output with 'buildman -s'

Overall it seems better to attribute a toolchain issue to the boards
that it affects. This results in clear failures which can be examined,
no matter what happened in the .bm-work directory previously.

So write a 'done' file for each build when a toolchain is missing.

The end result of this patch is to make missing toolchains much more
obvious. It should be things a bit easier for novice users.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Allow skipping the dtc build</title>
<updated>2024-09-26T10:40:30Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-08-15T19:57:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ba134c35316e275fd8708cf20794f61526d6420a'/>
<id>urn:sha1:ba134c35316e275fd8708cf20794f61526d6420a</id>
<content type='text'>
For most boards, the device-tree compiler is built in-tree, ignoring the
system version. Add a special option to skip this build. This can be
useful when the system dtc is up-to-date, as it speeds up the build.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Retry the build for current source</title>
<updated>2024-09-26T10:40:30Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-06-23T17:55:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bf984a6a0073f9a1bf7814ac44e72218afcb2081'/>
<id>urn:sha1:bf984a6a0073f9a1bf7814ac44e72218afcb2081</id>
<content type='text'>
Buildman retries a failed build when processing a branch, but does not
do this when building current source. It is useful to do this retry in
both cases, so add the logic for it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Revert "buildman: Always use the full path in CROSS_COMPILE"</title>
<updated>2024-07-08T15:12:34Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2024-07-05T20:34:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e13fcae3fce8b2c4db86339c9e8bafdd403f22b5'/>
<id>urn:sha1:e13fcae3fce8b2c4db86339c9e8bafdd403f22b5</id>
<content type='text'>
There are operations in buildman that result in running the cross-tools
(such as performing size checks) and now that we have not modified PATH
to know where our tools are, these operations fail.

This reverts commit 6c0a3cf75f72370deec3ee516a9dd377397af207.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>buildman: Always use the full path in CROSS_COMPILE</title>
<updated>2024-07-03T06:36:33Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-06-23T17:56:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6c0a3cf75f72370deec3ee516a9dd377397af207'/>
<id>urn:sha1:6c0a3cf75f72370deec3ee516a9dd377397af207</id>
<content type='text'>
The feature to set the toolchain path does not seem to be needed. It
causes problems with venv (see [1]). Let's remove it.

Add some tests while we are here.

It does not look like any docs changes are needed for this.

[1] https://patchwork.ozlabs.org/project/uboot/patch/20240621131423.2363294-6-sjg@chromium.org/

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Suggested-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Andrejs Cainikovs &lt;andrejs.cainikovs@toradex.com&gt;
</content>
</entry>
<entry>
<title>buildman: Add a flag to force mrproper on failure</title>
<updated>2024-07-03T06:36:33Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-06-23T17:55:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8941477e02717a7104f8400363979fc3831a4041'/>
<id>urn:sha1:8941477e02717a7104f8400363979fc3831a4041</id>
<content type='text'>
When a file is removed by a commit (e.g. include/common.h yay!) it can
cause incremental build failures since one of the dependency files from
a previous build may mention the file.

Add an option to run 'make mrproper' automatically when a build fails.
This can be used to automatically resolve the problem, without always
adding the large overhead of 'make mrproper' to every build.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Avoid rebuilding when --mrproper is used</title>
<updated>2024-07-03T06:36:33Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-06-23T17:55:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7e93bd30b1e2a00a46bb60f7122f79801bc0590b'/>
<id>urn:sha1:7e93bd30b1e2a00a46bb60f7122f79801bc0590b</id>
<content type='text'>
When this flag is enabled, 'make mrproper' is always used when
reconfiguring, so there is no point in doing it again.

Update this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
