From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] how to read the buildman report
Date: Thu, 14 Aug 2014 14:36:19 -0700 [thread overview]
Message-ID: <53ED2BD3.3080004@freescale.com> (raw)
Simon,
I need some help to understand the report of buildman. Use this example, when I
build all arm and powerpc boards,
$ tools/buildman/buildman -b working_qoriq arm powerpc -s
Summary of 19 commits for 1023 boards (24 threads, 1 job per thread)
01: ls102xa: dcu: Add platform support for DCU on LS1021ATWR board
arm: + tricorder_flash vf610twr tricorder
powerpc: + taishan dlvision
02: video: dcu: Add DCU driver support
03: video: dcu: Add Sii9022A HDMI Transmitter support
04: arm: ls102xa: Add LETECH support for LS1021AQDS/TWR board
05: serial: lpuart: add 32-bit registers lpuart support
06: net: tsec: Remove tx snooping support from LS1
arm: vf610twr
07: arm: ls102xa: Add basic support for LS1021ATWR board
08: arm: ls102xa: Add basic support for LS1021AQDS board
arm: + ls1021atwr_nor ls1021atwr_letech
09: driver/ddr/fsl: Add support of overriding chip select write leveling
arm: + ls1021aqds_nor ls1021aqds_letech
10: driver/ddr/freescale: Fix DDR3 driver for ARM
11: driver/ddr/freescale: Add support of accumulate ECC
12: ls102xa: esdhc: Add esdhc support for LS102xA
13: ls102xa: etsec: Add etsec support for LS102xA
14: net: mdio: Use mb() to be compatible for both ARM and PowerPC
15: net: mdio: Add private MDIO read/write function
16: net: Merge asm/fsl_enet.h into fsl_mdio.h
17: ls102xa: i2c: Add i2c support for LS102xA
18: arm: ls102xa: Add Freescale LS102xA SoC support
19: patman: Only use git's --no-decorate when available
First, is the build supposed to be top down or bottom up? It looks like buildman
starts to build from the last commit and works it way down. What I don't
understand is the new board. Under patch 08 and 09, I see two boards failed. But
these two boards don't exist until a later commit. Should I use --force-reconfig
switch?
Second, when I see a failed board under a commit, is this commit causing the
failure? It is not the case in my example. I see vf610twr failed under 01, but
the actual failure is caused by commit 05.
York
next reply other threads:[~2014-08-14 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 21:36 York Sun [this message]
2014-08-14 22:17 ` [U-Boot] how to read the buildman report Simon Glass
2014-08-14 22:33 ` York Sun
2014-08-14 23:21 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ED2BD3.3080004@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.