Hi autoconf Guru’s .. I am hoping that you can help out here .. I have a rather strange situation, that I am hoping you can shed some light on ..
I have been trying to get the autoconf make check tests to work under a couple of different scenarios and I am getting a failure in one of them that makes no sense .. After some extensive investigations, I am finally reluctantly turning to you for help as to why I am getting an error .. Situation: I run the "make check” command from a script on the command line, and the make check tests pass.. I then run the same script that passed on the command line, in a Jenkins Job, and one of the tests fails .. I though it may have been related to environment variables, but I have looked at both environments , and there does not seem to be any real difference .. I am have attached the log files for the test directory, in the hope that you can determine what the issue may be .. I ran the testsuite script to isolate the issue, and the results are listed below: Thanks for any help you can offer .. Cheers Dave W. Passing testsuite via command line: bash-4.1$ ./testsuite -e -k parallel ## ----------------------------- ## ## GNU Autoconf 2.68 test suite. ## ## ----------------------------- ## Autotest. 199: parallel test execution ok 200: parallel truth ok 201: parallel fallacy ok 202: parallel skip ok 203: parallel syntax error ok 204: parallel errexit ok 205: parallel autotest and signal handling ok 206: parallel args but non-working mkfifo ok ## ------------- ## ## Test results. ## ## ------------- ## All 8 tests were successful. Failing testsuite via Jenkins Job Execution: + env TOMCAT_HOME=/auto/swtools/jenkins/master/apache-tomcat-6.0.18 BUILD_URL=http://swtools-620-001:8080/job/env_test/29/ TERM=linux HUDSON_SERVER_COOKIE=2411d72a565874f3 BUILD_TAG=jenkins-env_test-29 WORKSPACE=/auto/swtools/jenkins/master/workspace/env_test JOB_URL=http://swtools-620-001:8080/job/env_test/ PRODUCTION_BUILD=1 IBM_JAVA_COMMAND_LINE=java -jar /auto/swtools/jenkins/master/jenkins.war -DJENKINS_HOME=/auto/swtools/jenkins/master JENKINS_HOME=/auto/swtools/jenkins/master PATH=/sw/licensed/sun/jdk/1.7.0_55/jre/bin::/router/bin:/usr/cisco/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin:/usr/local/bin BUILD_CAUSE_MANUALTRIGGER=true RUNLEVEL=3 PWD=/auto/swtools/jenkins/master/workspace/env_test LANGSH_SOURCED=1 JAVA_HOME=/sw/licensed/sun/jdk/1.7.0_55/jre HUDSON_URL=http://swtools-620-001:8080/ LANG=en_US.UTF-8 JOB_NAME=env_test previous=N BUILD_DISPLAY_NAME=#29 PREVLEVEL=N BUILD_ID=29 JENKINS_URL=http://swtools-620-001:8080/ CATALINA_OPTS=-DJENKINS_HOME=/auto/swtools/jenkins/master/jenkins-home -Xmx512m -Djava.awt.headless=true BUILD_CAUSE=MANUALTRIGGER JENKINS_WAR=/auto/swtools/jenkins/master/jenkins.war CONSOLETYPE=vt HOME=/auto/swtools/jenkins SHLVL=4 JENKINS_SERVER_COOKIE=2411d72a565874f3 EXECUTOR_NUMBER=0 CATALINA_PID=/auto/swtools/jenkins/master/jenkins-tomcat.pid SWXREPO_LOC=/auto/swtools/prod/SWToolsBuildInstructions NODE_LABELS=MASTER master SWXREPO_STAGING_LOC=/auto/swtools/prod/SWToolsBuildInstructions_staging JENKINS_BASEDIR=/auto/swtools/jenkins/master UPSTART_EVENTS=runlevel HUDSON_HOME=/auto/swtools/jenkins/master SELECT=package BUILD_NUMBER=29 UPSTART_JOB=rc HUDSON_COOKIE=acf46385-9731-4fc4-9f74-6bc7a2fc0b9d JENKINS_CONFIG=/auto/swtools/jenkins/master/config.xml _=/bin/env + cd /auto/swtools/prod-builds/build/Linux-rhel6.0-cel-6.20/autoconf-2.68/autoconf/autoconf-2.68/tests + ./testsuite -e -k parallel ## ----------------------------- ## ## GNU Autoconf 2.68 test suite. ## ## ----------------------------- ## Autotest. 199: parallel test execution ok 200: parallel truth ok 201: parallel fallacy ok 202: parallel skip ok 203: parallel syntax error ok 204: parallel errexit ok 205: parallel autotest and signal handling FAILED (autotest.at:1566) ## ------------- ## ## Test results. ## ## ------------- ## ERROR: 7 tests were run, one failed unexpectedly and inhibited subsequent tests. ## -------------------------- ## ## testsuite.log was created. ## ## -------------------------- ## Please send per-test log files and all information you think might help: To: <bug-autoconf@gnu.org> Subject: [GNU Autoconf 2.68] testsuite: 205 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. Build step 'Execute shell' marked build as failure Finished: FAILURE David A. Watson Cisco Canada 3000 Inovation Dr Kanata, On K2K 3E8 613 254-3377 Be the change that you want to see in the world !
205.tar.gz
Description: 205.tar.gz