SparkBuild error not present in regular build

Replies to This Discussion

Permalink Reply by Yuri Shtil on October 27, 2009 at 5:47pm

There you go. The full script attached, it is very short.

Attachments:

• script.sh, 3 KB

Permalink Reply by Duc Nguyen on October 27, 2009 at 6:25pm

since the script is so simple, could you try logging directly onto the commander resource that was used to run it originally, and run the script directly from there? I'm trying to figure out if it's something in the commander environment that is tripping up emake.

Thanks.

Permalink Reply by Yuri Shtil on October 28, 2009 at 3:32pm

Duc,

It was all my fault. We run more on more than one resource but I specified the same paths for both
steps, I separated the xml and db paths and everything is better now.
I don't want the huge log files, how do I lower the verbosity?

• ▶ Reply

Permalink Reply by Yuri Shtil on October 28, 2009 at 4:06pm

However, the annotation files are full with things like
I cannot put here.

I guess makefiles echo special characters and the file would not load.

• ▶ Reply

Permalink Reply by Duc Nguyen on October 28, 2009 at 4:56pm

I am not sure what you mean by this. Is postp still picking up WARNING/ERROR strings from the annotation file?

• ▶ Reply

Permalink Reply by Yuri Shtil on October 29, 2009 at 8:22am

I attached one of the annotation files. Try to open it with sbinsight.

Attachments:

• i386.phase1.xml.gz, 412 KB

• ▶ Reply

Permalink Reply by Yuri Shtil on October 29, 2009 at 3:33pm

Hi Duc,

Did you have a chance to look into this?

• ▶ Reply

Permalink Reply by Eric Melski on October 29, 2009 at 4:08pm

Yuri, it looks like there are two types of problems with the annotation file. First, you are using the 'clear' command in the middle of your build for some reason. This emits control characters that are normally interpreted by the terminal to clear the screen. This obviously doesn't make much sense in the context of an automated build. Unfortunately, those control characters are not valid in raw form in an XML document. The easiest thing to do is strip those characters out of the annotation before trying to load it. I will log a bug report for this issue, but I don't know when we will be able to address it.

Second, the annotation appears to be truncated. It just stops shortly after the command that prints "Building: Pci9030". This could be caused by a variety of things -- the build was aborted, or the file was written to a network drive that had connectivity problems, etc.

Hope that helps,

Eric Melski
Architect
Electric Cloud, Inc.

• ▶ Reply

Permalink Reply by Yuri Shtil on October 29, 2009 at 4:53pm

The compilation aborts with the following error message:
checking whether make sets $(MAKE)... ./configure: eval: line 20417: syntax error near unexpected token `<'
./configure: eval: line 20417: `

• ▶ Reply

Permalink Reply by Yuri Shtil on October 30, 2009 at 1:24pm

I guess the problem is that the build scripts deep inside call make and try to use its output, emake annotates the output which look like garbage to the code reading it.

• ▶ Reply

Permalink Reply by Eric Melski on October 30, 2009 at 1:39pm

Yuri, that's an interesting discovery! Hopefully in a future release we'll be able to make SparkBuild emake write annotation to a file the same way that ElectricAccelerator emake does.

Best Regards,

Eric Melski
Architect
Electric Cloud, Inc.

Permalink Reply by Duc Nguyen on October 28, 2009 at 4:53pm

If the problem has went away, then you can just turn off logging entirely by removing the --emake-logfile and --emake-debug flags.

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• 4
• Next ›
• Page