SparkBuild Community

Pushing the envelope of build performance

Yuri Shtil

SparkBuild error not present in regular build

I get a number of errors introduced by SparkBuild:

--- Start Quote ---
Step 'compilation' - 3 Errors, 291 Warnings
error Error #1 of 3 in step 'compilation'
log referencecompilation.353053.log:61579 (src)

Views: 6

▶ Reply to This

Replies to This Discussion

Yuri ShtilPermalink Reply by Yuri Shtil on October 19, 2009 at 3:37pm
For some reason the message got truncated, here is the correct message:

I get a number of errors introduced by SparkBuild:

--- Start Quote ---
Warning #1 of 60 in step 'compilation'
log referencecompilation.354422.log:39
WARNING EC1155: Invalid subbuild db file path


--end quote
I see no errors when using gnu make.
I also see a large number of warnings like:

Warning #1 of 60 in step 'compilation'
log referencecompilation.354422.log:39
WARNING EC1155: Invalid subbuild db file path
Duc NguyenPermalink Reply by Duc Nguyen on October 19, 2009 at 4:05pm
Is this your top level make instance that is generating the warning, or is it a submake? If it is a submake, how are you invoking the submake in your build?

Would it be possible for you to provide emake debug logging? (--emake-debug=jpn --emake-logfile=dlog)
Yuri ShtilPermalink Reply by Yuri Shtil on October 19, 2009 at 5:09pm
The way I invoke this is:
- created a symlink in the emake installation directory pointing to the emake executable
- prepended the the emake installation directory to the PATH
- ran the build as usual, whenever make is called it invokes emake

I attached the log files, the jpn I could not find
Attachments:
Eric MelskiPermalink Reply by Eric Melski on October 19, 2009 at 4:06pm
Yuri, what's the command line you used to invoke emake? It looks like you invoked emake with a non-existent filename for --emake-subbuild-db, without the --emake-gen-subbuild-db=1 option.

Hope that helps,

Eric Melski
Architect
Electric Cloud, Inc.
Yuri ShtilPermalink Reply by Yuri Shtil on October 20, 2009 at 8:25am
Thank you Eric, it was missing ...
I attached all related files created by the latest (failed) build.
Attachments:
Eric MelskiPermalink Reply by Eric Melski on October 20, 2009 at 2:51pm
Yuri, I'm not sure why you say this is a failed build. I agree there are some issues loading the annotation from phase1 in SparkBuild Insight, but it appears that the build ran to completion successfully. There are no jobs marked as have a non-zero exit code, and nothing that looks like an error in the build output. Can you provide some more explanation?

Thanks,

Eric Melski
Architect
Electric Cloud, Inc.
Yuri ShtilPermalink Reply by Yuri Shtil on October 21, 2009 at 8:19am
Well, I concluded that the job failed because the job page said so.
I attached two screen shots to illustrate my point.
Attachments:
Eric MelskiPermalink Reply by Eric Melski on October 21, 2009 at 1:56pm
A-ha, I see the trouble: you've enabled annotation on the build, so now Commander's postp matcher is scanning the annotated build log, rather than the "normal" build log. The annotated log, of course, contains all the command-lines for all the commands that were executed by the build, including this one:

test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo;

As you can see, the 'echo "ERROR ..."' will only be run under specific conditions, and in fact it was not run in your build -- but postp is not smart enough to distinguish between this text, which is just a command-line, and output text that would have appeared in the normal build log.

I believe the easiest fix is to use the standard Unix utility tee to save a copy of the annotation to a different file than the build log, and anno2log, which should have been installed with SparkBuild emake, to convert the annotation back to a normal build log. That is, you need to change your emake invocation from this:

emake --emake-annodetail=basic,env,waiting

... to this:

emake --emake-annodetail=basic,env,waiting | tee build.anno | anno2log

Hope that helps,

Eric Melski
Architect
Electric Cloud, Inc.
Yuri ShtilPermalink Reply by Yuri Shtil on October 21, 2009 at 2:25pm
Well, anno2log produced a slew of errors like:
WARNING EC1155: SubBuild::connect(39938) error: couldn't connect to server: Connection refused (error code 0x6f)
Attachments:
Eric MelskiPermalink Reply by Eric Melski on October 21, 2009 at 2:43pm
Yuri, this warning is not coming from anno2log but from emake, but besides that I can't tell you much else without more information. The images you attached appear to be the same images you attached to a previous message, so they are not useful. Is this new warning message reproducible? Can you generate an emake debug log by adding --emake-debug=jn --emake-logfile=emake.dlog, then upload emake.dlog?

Thanks,

Eric Melski
Architect
Electric Cloud, Inc.
Yuri ShtilPermalink Reply by Yuri Shtil on October 21, 2009 at 3:05pm
I have made the changes you recommended and now I'm getting hundreds of errors like:

WARNING EC1155: SubBuild::connect(39938) error: couldn't connect to server: Connection refused (error code 0x6f)
Eric MelskiPermalink Reply by Eric Melski on October 21, 2009 at 3:42pm
Yuri, what is the exact command-line you are using now? Can you generate the debug log I requested and upload that?

Thanks,

Eric Melski
Architect
Electric Cloud, Inc.

RSS

Share

© 2012   Created by Electric Cloud Administrator.

Badges  |  Report an Issue  |  Terms of Service