From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman: suspect issue with patman tags
Date: Wed, 27 Aug 2014 14:22:07 -0700 [thread overview]
Message-ID: <53FE4BFF.4070001@broadcom.com> (raw)
In-Reply-To: <D9A82E139BA378458BD9D956A07ACA3A2AEEF4F9@SJEXCHMB10.corp.ad.broadcom.com>
Another issue may be related to the "combined issue" below....)
Five consecutive builds (with no changes between builds)
(1)does not always generate the "u-boot.bin" file
(2)random error messages ?!?!?
Is anyone else seeing these issues?
(please don't delete MAKEALL yet !!!!)
Thanks, Steve
srae at host1:~/work/to_denx$ tools/buildman/buildman bcm28155_ap
No section: 'make-flags'
Could not find ./boards.cfg
Generating boards.cfg ... (jobs: 8)
1171/1171 [=======================================================>]
Building current source for 2 boards (2 threads, 4 jobs per thread)
0 0 2 /2 0:00:06 : bcm28155_ap
srae at host1:~/work/to_denx$ find .. -name "u-boot.[mb]*" -exec ls -l {} \;
-rw-r--r-- 1 srae srae 239004 Aug 26 15:34
../current/.bm-work/00/build/u-boot.map
-rw-r--r-- 1 srae srae 245242 Aug 26 15:34
../current/.bm-work/01/build/u-boot.map
-rw-r--r-- 1 srae srae 190100 Aug 26 15:34
../current/.bm-work/01/build/u-boot.bin
srae at host1:~/work/to_denx$ tools/buildman/buildman bcm28155_ap
No section: 'make-flags'
Building current source for 2 boards (2 threads, 4 jobs per thread)
0 0 2 /2 0:00:06 : bcm28155_w1d
srae at host1:~/work/to_denx$ find .. -name "u-boot.[mb]*" -exec ls -l {} \;
-rw-r--r-- 1 srae srae 239004 Aug 26 15:36
../current/.bm-work/00/build/u-boot.map
-rw-r--r-- 1 srae srae 245242 Aug 26 15:36
../current/.bm-work/01/build/u-boot.map
srae at host1:~/work/to_denx$ tools/buildman/buildman bcm28155_ap
No section: 'make-flags'
Building current source for 2 boards (2 threads, 4 jobs per thread)
arm: + bcm28155_w1d
+make[1]: *** [checkarmreloc] Error 1
+make: *** [sub-make] Error 2
0 0 2 /2 0:00:06 : bcm28155_ap
srae at host1:~/work/to_denx$ find .. -name "u-boot.[mb]*" -exec ls -l {} \;
-rw-r--r-- 1 srae srae 239004 Aug 26 15:37
../current/.bm-work/00/build/u-boot.map
-rw-r--r-- 1 srae srae 189744 Aug 26 15:37
../current/.bm-work/00/build/u-boot.bin
-rw-r--r-- 1 srae srae 245242 Aug 26 15:37
../current/.bm-work/01/build/u-boot.map
-rw-r--r-- 1 srae srae 190100 Aug 26 15:37
../current/.bm-work/01/build/u-boot.bin
srae at host1:~/work/to_denx$ tools/buildman/buildman bcm28155_ap
No section: 'make-flags'
Building current source for 2 boards (2 threads, 4 jobs per thread)
arm: + bcm28155_w1d
+make[1]: *** [checkarmreloc] Error 1
+make: *** [sub-make] Error 2
0 0 2 /2 0:00:06 : bcm28155_ap
srae at host1:~/work/to_denx$ find .. -name "u-boot.[mb]*" -exec ls -l {} \;
-rw-r--r-- 1 srae srae 239004 Aug 26 15:37
../current/.bm-work/00/build/u-boot.map
-rw-r--r-- 1 srae srae 245242 Aug 26 15:37
../current/.bm-work/01/build/u-boot.map
-rw-r--r-- 1 srae srae 190100 Aug 26 15:37
../current/.bm-work/01/build/u-boot.bin
srae at host1:~/work/to_denx$ tools/buildman/buildman bcm28155_ap
No section: 'make-flags'
Building current source for 2 boards (2 threads, 4 jobs per thread)
arm: + bcm28155_w1d
+make[1]: *** [checkarmreloc] Error 1
+make: *** [sub-make] Error 2
0 0 2 /2 0:00:05 : bcm28155_w1d
srae at host1:~/work/to_denx$ find .. -name "u-boot.[mb]*" -exec ls -l {} \;
-rw-r--r-- 1 srae srae 239004 Aug 26 15:39
../current/.bm-work/00/build/u-boot.map
-rw-r--r-- 1 srae srae 245242 Aug 26 15:39
../current/.bm-work/01/build/u-boot.map
srae at host1:~/work/to_denx$
*From:*Steve Rae
*Sent:* Monday, August 25, 2014 09:06
*To:* Simon Glass
*Subject:* buildman: issue with patman tags
Simon,
When I combine multiple patch-series, each with their own patman tags in
the commit messages, into a single branch...
Then:
$ tools/buildman/buildman -b combined bcm28155_ap
No section: 'make-flags'
Traceback (most recent call last):
File "tools/buildman/buildman", line 139, in <module>
control.DoBuildman(options, args)
File "/home/srae/work/to_denx/tools/buildman/control.py", line 161,
in DoBuildman
options.git_dir, count)
File
"/home/srae/work/to_denx/tools/buildman/../patman/patchstream.py", line
387, in GetMetaDataForList
ps.ProcessLine(line)
File
"/home/srae/work/to_denx/tools/buildman/../patman/patchstream.py", line
248, in ProcessLine
self.AddToSeries(line, name, value)
File
"/home/srae/work/to_denx/tools/buildman/../patman/patchstream.py", line
94, in AddToSeries
self.series.AddTag(self.commit, line, name, value)
File "/home/srae/work/to_denx/tools/buildman/../patman/series.py",
line 67, in AddTag
(commit.hash, line, values, self[name]))
ValueError: In 442a87cd: line 'Series-version: 1': Cannot add another
value '['1']' to series '4'
$
Note: each patch-series individually build successfully with buildman,
it is only after I combine that there are issues....
Thanks, Steve
next parent reply other threads:[~2014-08-27 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D9A82E139BA378458BD9D956A07ACA3A2AEEF4F9@SJEXCHMB10.corp.ad.broadcom.com>
2014-08-27 21:22 ` Steve Rae [this message]
2014-08-28 14:45 ` [U-Boot] buildman: suspect issue with patman tags Simon Glass
2014-08-28 17:21 ` Steve Rae
2014-08-29 0:59 ` Simon Glass
2014-08-29 16:58 ` Steve Rae
2014-09-01 5:10 ` 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=53FE4BFF.4070001@broadcom.com \
--to=srae@broadcom.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