On Thu, Mar 16, 2023 at 10:56:17AM -0400, Tom Rini wrote:
On Thu, Mar 16, 2023 at 07:58:33AM -0600, Simon Glass wrote:
Hi Tom,
On Wed, 15 Mar 2023 at 08:49, Tom Rini trini@konsulko.com wrote:
On Tue, Mar 14, 2023 at 04:07:57PM -0600, Simon Glass wrote:
Hi Tom,
On Mon, 13 Mar 2023 at 13:36, Tom Rini trini@konsulko.com wrote:
On Sun, Mar 12, 2023 at 09:10:19PM -0600, Simon Glass wrote:
Hi Tom,
This is for the -next branch
https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/15568
The following changes since commit bcf343146ff365a88481b9a80920ed146c6dee5b:
Merge tag 'dm-next-9mar23' of https://source.denx.de/u-boot/custodians/u-boot-dm into next (2023-03-09 11:22:50 -0500)
are available in the Git repository at:
git://git.denx.de/u-boot-dm.git tags/dm-next-12mar23
for you to fetch changes up to 7bb28330f7b4d20bcf844ec306dcfbb41296cfa8:
buildman: Fix CROSS_COMPILE output for sandbox (2023-03-12 11:37:34 -0600)
There's something, or somethings, broken here now. Take a look at: https://source.denx.de/u-boot/u-boot/-/jobs/593223#L904 where now there's a bunch of warnings but we don't fail the build (nor
That seems to have been going for a while. See:
I don't see it there, no. The problem, to be clear, is warnings in C NOT leading to CI failing.
OK that's fine, but what does it have to do with this pull request?
I don't know when this regression happened, only that I saw it, and the warnings at the same time. So I'm seeing now (after sorting out some failing lab equipment) if the "C warnings cause CI to fail" changes are in master, or next, or neither.
Alright, so, there was something very odd with what got triggered before, as I cannot make CI pass when it should fail with a simple #warning. I'll review this PR fully now.