To compare the Jenkins and local environments run from a shell

Jenkins job
#!/bin/bash -x
env | sort > jenkins_env.txt

and archive the file jenkins_env.txt

Locally from a shell on the slave
env | sort > manual_env.txt

Then save these files to a common place and compare with 
your preferred compare tool.

>From the logs below it looks like you should check to see if you are using 
the same versions of armlink, as the arm pages for the armlink 4.1 options 
seem to indicate using a --keep=dretinf.o(*) rather than  --keep 
dretinf.o(*) of older versions

http://infocenter.arm.com/help/topic/com.arm.doc.dui0381b/CHDJGJEC.html

The other thing to look at is the command that is being called for the 
linking of the sensorsimg.elf, which I expect will be defined 
in the Makefile or is included from it.
 located under /data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/bsp/sensorsimg/build/ 
arm7/sensorsimg/arm7/DSPSBLDZ/ 

Check for any Variables used in that command, and see if they are different 
between the runs.

I expect that you will find something slightly different that will cause 
this error, as we have had this many times before in our builds where a 
env Variable was not set or set incorrectly on the jenkins job, where the 
build expected this to be set correctly.

On Friday, 2 March 2012 01:06:18 UTC, seonguk.baek wrote:
>
> Thanks for your reply :-) 
>
> On 3월2일, 오전2시05분, cjo <cjo.john...@gmail.com> wrote: 
> > From the error described, it looks like the errors are coming from 
> another 
> > script called from inside the shell command. 
> > 
> > Are the "sh: -c: line 0: ..." 
> > showing up in the build log in Jenkins? 
> Yes 
> > 
> > Can you share more or the output log? (basically 15-20 lines before this 
> is 
> > seen) 
> attched end of this 
>
> > As it looks more likely that the errors are coming from a script that is 
> > being called from ./build_target.sh or Make. 
> > 
> > Does the log show what script is being called before the error is 
> printed? 
> No 
>
> > 
> > Does running the same commands manually from the slave machine show the 
> > same issue? 
> There are no errors when I run manually in slave machine. 
>
> > If not trying doing a diff of the env from the jenkins job and the 
> manual 
> > run to see what differences there are. 
> > 
> > Chris 
> /data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/systemdrivers/hal/ipcint/ 
> ....
> === Compiling  sensorsimg/arm7/DSPSBLDZ/tramp_pic.c 
> === Compiling  sensorsimg/arm7/DSPSBLDZ/tramp_pic_ucos.c 
> "/data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/systemdrivers/tramp/src/ 
> platform/pic/tramp_pic.c", line 744: Warning:  #177-D: variable 
> "index" was declared but never referenced 
>     uint32                   flags,index; 
>                                    ^ 
> === Compiling  sensorsimg/arm7/DSPSBLDZ/tramp_pic_log.c 
> /data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/systemdrivers/tramp/src/ 
> platform/pic/tramp_pic.c: 1 warning, 0 errors 
> === Compiling  sensorsimg/arm7/DSPSBLDZ/tramp_pic_bsp_sps.c 
> === Compiling  sensorsimg/arm7/DSPSBLDZ/tramp_gpio_sps.c 
> /data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/systemdrivers/hal/gsbi/ 
> src/HALgsbi.c: 4 warnings, 0 errors 
> === Archiving  sensorsimg/arm7/DSPSBLDZ/HALgsbi.lib 
> === Archiving  sensorsimg/arm7/DSPSBLDZ/DALtlmm.lib 
> === Archiving  sensorsimg/arm7/DSPSBLDZ/DalIPCInt.lib 
> === Archiving  sensorsimg/arm7/DSPSBLDZ/tramp.lib 
> === Linking    sensorsimg/arm7/DSPSBLDZ/sensorsimg.elf 
> sh: -c: line 0: syntax error near unexpected token `(' 
> sh: -c: line 0: `/opt/RVCT41P7/RVCT/Programs/4.1/713/linux-pentium/ 
> armlink --elf --map --info sizes,totals --list /data001/jenkins/ 
> jenkinsbuild/jenkinsbuild/workspace/devbuild_g1_dsps_proc/non_HLOS/ 
> dsps_proc/core/bsp/sensorsimg/build/arm7/sensorsimg/arm7/DSPSBLDZ/ 
> sensorsimg.map --symbols --symdefs /data001/jenkins/jenkinsbuild/ 
> jenkinsbuild/workspace/devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/ 
> bsp/sensorsimg/build/arm7/sensorsimg/arm7/DSPSBLDZ/sensorsimg.sym -- 
> scatter /data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/bsp/sensorsimg/build/ 
> arm7/sensorsimg/arm7/DSPSBLDZ/sensorsimg.scl --noremove --feedback 
> dsps_linker_feedback.txt --diag_suppress=L6314,L6329,L6319 -- 
> info=unused,unusedsymbols --no_strict_ph --remove --keep dretinf.o(*) 
> --keep dnaninf.o(*) --keep dcmpi.o(*) --keep llshl.o(*) --keep 
> llsshr.o(*) --keep llmul.o(*) --keep llsdiv.o(*) --keep lludiv.o(*) -- 
> keep aeabi_memset.o(*) --keep rt_memcpy.o(*) --keep rt_memcpy_w.o(*) -- 
> keep rt_memclr.o(*) --keep rt_memclr_w.o(*) --keep strncpy.o(*) --keep 
> strncmp.o(*) --keep uread4.o(*) --keep uwrite4.o(*) --keep 
> aeabi_idiv0_sigfpe.o(*) --keep aeabi_ldiv0_sigfpe.o(*) --keep 
> use_no_semi.o(*) --keep rt_div0.o(*) --keep defsig_fpe_formal.o(*) -- 
> keep d2f.o(*) --keep daddsub_noclz.o(*) --keep trapv.o(*) --keep 
> ddiv.o(*) --keep dflt_noclz.o(*) --keep retnan.o(*) --keep 
> fretinf.o(*) --keep aeabi_sdiv.o(*) --keep dfix.o(*) --keep dleqf.o(*) 
> --keep ffix.o(*) --keep dcheck1.o(*) --keep dmul.o(*) --keep 
> fflt_noclz.o(*) --keep fmul.o(*) --keep scalbn.o(*) --keep 
> fnaninf.o(*) "/data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/buses/i2c/dal/build/ 
> sensorsimg/arm7/DSPSBLDZ/DALi2c.lib" "/data001/jenkins/jenkinsbuild/ 
> jenkinsbuild/workspace/devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/ 
> buses/i2c/dalpd/qup/build/sensorsimg/arm7/DSPSBLDZ/DALQupI2cPd.lib" "/ 
> ....
>
 

> dsps_proc/core/bsp/sensorsimg/build/arm7/sensorsimg/arm7/DSPSBLDZ/ 
> sensorsimg.elf"' 
> scons: *** [/data001/jenkins/jenkinsbuild/jenkinsbuild/workspace/ 
> devbuild_g1_dsps_proc/non_HLOS/dsps_proc/core/bsp/sensorsimg/build/ 
> arm7/sensorsimg/arm7/DSPSBLDZ/sensorsimg.elf] Error 1 
> scons: building terminated because of errors

Reply via email to