public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] help on using buildman
Date: Thu, 20 Nov 2014 11:46:12 -0800	[thread overview]
Message-ID: <546E4504.5040906@freescale.com> (raw)
In-Reply-To: <546E3F77.9010503@freescale.com>

On 11/20/2014 11:22 AM, York Sun wrote:
> On 11/20/2014 11:13 AM, Simon Glass wrote:
>> You can only see the make output if you comment out this line in
>> builderthread.py:
>>
>>                 #args.append('-s')
>>
>> Then it will be in a file called 'log'. It would be nice to have an
>> option for that...
>>
> 
> Let me try that.
> 

I made the change to file tools/buildman/builderthread.py

-                args.append('-s')
+#                args.append('-s')

I run it again for one commit and with one board

$ ./tools/buildman/buildman -b working_upstream_qoriq --count=1 --keep-outputs
--force-build --force-reconfig MPC832XEMDS_HOST_66 -ve
No section: 'make-flags'
boards.cfg is up to date. Nothing to do.
Building 1 commit for 1 boards (1 thread, 24 jobs per thread)
Cloning repo for thread 0
01: arm: ls102xa: Select ge2_clk125 for eTSEC clock muxing
   powerpc: +   MPC832XEMDS_HOST_66
+make[1]: *** No rule to make target `../arch//cpu/u-boot.lds', needed by
`u-boot.lds'.  Stop.
+make: *** [sub-make] Error 2
    0    0    1 /1      MPC832XEMDS_HOST_66

$ ll
../working_upstream_qoriq/01_of_01_g3b33b926_arm--ls102xa--Select/MPC832XEMDS_HOST_66/
total 28
-rw-rw-r-- 1 jenkins jenkins 11588 Nov 20 13:28 autoconf.mk
-rw-rw-r-- 1 jenkins jenkins     1 Nov 20 13:28 done
-rw-rw-r-- 1 jenkins jenkins   168 Nov 20 13:28 err
-rw-rw-r-- 1 jenkins jenkins   939 Nov 20 13:28 log
-rw-rw-r-- 1 jenkins jenkins   276 Nov 20 13:28 toolchain

I don't see much useful information in file log

$ cat
../working_upstream_qoriq/01_of_01_g3b33b926_arm--ls102xa--Select/MPC832XEMDS_HOST_66/log

make[1]: Entering directory
`/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
  GEN     ./Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
  CHK     include/config.h
  UPD     include/config.h
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
make[1]: Leaving directory
`/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
make[1]: Entering directory
`/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'
  CHK     include/config/uboot.release
  CHK     include/generated/timestamp_autogenerated.h
  GEN     ./Makefile
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/config/uboot.release
make[1]: Leaving directory
`/local/jenkins/jobs/york-scm-test-upstream-before-requesting-pull/working_upstream_qoriq/.bm-work/00/build'

Nothing more than that. Where shall I look for ARCH?

If I build for board T4240QDS, it has error on most but not all. T4240QDS
T4240QDS_SRIO_PCIE_BOOT T4240QDS_SECURE_BOOT failed, but T4240QDS_NAND didn't.

York

  reply	other threads:[~2014-11-20 19:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 18:47 [U-Boot] help on using buildman York Sun
2014-11-20 19:13 ` Simon Glass
2014-11-20 19:22   ` York Sun
2014-11-20 19:46     ` York Sun [this message]
2014-11-20 19:51       ` Simon Glass
2014-11-20 19:55         ` York Sun
2014-11-20 20:10           ` Simon Glass
2014-11-20 20:18             ` York Sun
2014-11-20 21:04               ` York Sun
2014-11-20 21:33                 ` York Sun
2014-11-20 21:34                   ` York Sun
2014-11-20 21:46                     ` Simon Glass
2014-11-20 22:25                       ` York Sun
2014-11-20 23:35                         ` York Sun
2014-11-21  4:14                           ` Simon Glass
2014-11-21  4:42                             ` Masahiro Yamada
2014-11-21  4:53                               ` Masahiro Yamada
2014-11-21  4:55                               ` York Sun
2014-11-21  6:00                                 ` Masahiro Yamada
     [not found]                                   ` <E5C75E70-6F62-4E5C-9861-1D903D9BBFC9@freescale.com>
2014-11-21  6:47                                     ` York Sun
2014-11-21 17:14                                       ` York Sun
2014-11-21 17:22                             ` York Sun

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=546E4504.5040906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox