From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] help on using buildman
Date: Thu, 20 Nov 2014 14:25:45 -0800 [thread overview]
Message-ID: <546E6A69.2010103@freescale.com> (raw)
In-Reply-To: <CAPnjgZ3U585=eCt3hORd0oShi9M6_gF37ob0bcXviYg1uwiBEw@mail.gmail.com>
On 11/20/2014 01:46 PM, Simon Glass wrote:
> Hi York,
>
> On 20 November 2014 21:34, York Sun <yorksun@freescale.com> wrote:
>> On 11/20/2014 01:33 PM, York Sun wrote:
>>> On 11/20/2014 01:04 PM, York Sun wrote:
>>>> On 11/20/2014 12:18 PM, York Sun wrote:
>>>>>
>>>>> I don't see ARCH defined anywhere.
>>>>>
>>>>
>>>> Simon,
>>>>
>>>> I think ARCH is defined in Kconfig as SYS_ARCH. Is it possible buildman runs
>>>> out-of-order?
>>>>
>>>
>>> There is something. When the server is under heavy load, this error doesn't
>>> show. When the server is mostly idling, the error comes. Any suggestion to debug it?
>>
>> Scratch that. It is not consistent.
>
> It's a mystery to me. I haven't seen this problem in much usage and
> can only suggest digging in to figure it out.
>
Found something but not the root cause yet. For the failure run, it runs in
Makefile, passed include/config/uboot.release, but not anything under
"prepare3:". For the success run, it continues to run.
-bash-3.2$ more 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-p
ull/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'
echo "York debug here"
York debug here
CHK include/config/uboot.release
CHK include/generated/timestamp_autogenerated.h
GEN ./Makefile
UPD include/generated/timestamp_autogenerated.h
UPD include/config/uboot.release
echo "Done uboot.release"
Done uboot.release
(note, for the success run, the log would have "Using .. as source for U-Boot" here)
make[1]: Leaving directory
`/local/jenkins/jobs/york-scm-test-upstream-before-requesting-p
ull/working_upstream_qoriq/.bm-work/00/build'
Not sure if this is still buildman related, but only visible when running with
buildman.
York
next prev parent reply other threads:[~2014-11-20 22:25 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
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 [this message]
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=546E6A69.2010103@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