Are you running on 'master' nodes? I remember seeing an issue where with a recent version of Jenkins or a plugin where it doesn't execute jobs on the master node. But when run on non-master jenkins slaves, it works fine.
-----Original Message----- From: Tang Chen [mailto:[email protected]] Sent: Thursday, July 23, 2015 12:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system. Hi, all The Jenkins jobs submitted by zuul are always "pending-Waiting for next available executor" . And Jenkins log shows the following: Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl submitFunction WARNING: ---- Worker _exec-0 exception while executing function hudson.plugins.gearman.StartJobWorker java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.CancellationException at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:136) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:22) at hudson.plugins.gearman.MyGearmanWorkerImpl.submitFunction(MyGearmanWorkerImpl.java:590) at hudson.plugins.gearman.MyGearmanWorkerImpl.work(MyGearmanWorkerImpl.java:374) at hudson.plugins.gearman.AbstractWorkerThread.run(AbstractWorkerThread.java:166) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.util.concurrent.CancellationException at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:116) at org.gearman.worker.AbstractGearmanFunction.call(AbstractGearmanFunction.java:125) ... 5 more Caused by: java.util.concurrent.CancellationException at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:77) at hudson.plugins.gearman.StartJobWorker.safeExecuteFunction(StartJobWorker.java:196) at hudson.plugins.gearman.StartJobWorker.executeFunction(StartJobWorker.java:114) ... 6 more Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: ---- Worker _exec-0 sending initial grab job Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl handleSessionEvent INFO: ---- Worker _exec-1 received unique job assignment Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.MyGearmanWorkerImpl work INFO: ---- Worker _exec-1 executing function Jul 24, 2015 11:09:04 AM hudson.plugins.gearman.StartJobWorker safeExecuteFunction INFO: ---- Worker _exec-1 scheduling devstack-vm-test build #14 on with UUID 83d4fd10c1ad4f1ead51beb2adf23ccd and build params [(StringParameterValue) BASE_LOG_PATH='03/204803/1', (StringParameterValue) ZUUL_PIPELINE='check', (StringParameterValue) ZUUL_UUID='83d4fd10c1ad4f1ead51beb2adf23ccd', (StringParameterValue) LOG_PATH='03/204803/1/check/devstack-vm-test/83d4fd1', (StringParameterValue) ZUUL_CHANGE_IDS='204803,1', (StringParameterValue) ZUUL_PATCHSET='1', (StringParameterValue) ZUUL_BRANCH='master', (StringParameterValue) ZUUL_REF='refs/zuul/master/Z07d022076a68448d842bd1a47dd42e19', (StringParameterValue) ZUUL_COMMIT='174cac545549f086e07f32edbe34b70c4155a7fc', (StringParameterValue) ZUUL_URL='http://10.124.196.205/p/', (StringParameterValue) ZUUL_CHANGE='204803', (StringParameterValue) ZUUL_CHANGES='openstack-dev/sandbox:master:refs/changes/03/204803/1', (StringParameterValue) ZUUL_PROJECT='openstack-dev/sandbox'] It seems that Gearman doesn't work properly. Do you guys have any idea of this ? Thanks. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
