[openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

Tang Chen tangchen at cn.fujitsu.com
Fri Jul 24 06:20:43 UTC 2015


On 07/24/2015 12:59 PM, Zaro wrote:
> Hello Tang,  Openstack slaves only have a single executor so what you 
> are probably seeing is due to using build slaves that have multiple 
> executors.  There were a few bugs[1] that was fixed recently around 
> these types of deadlock issues. The new gearman-plugin release[2] 
> contains fixes for those issues.  Also if you want to test the 
> gearman-plugin with Jenkins independently of zuul you can use the 
> simple gearman-plugin-client[3] to send jobs your gearman server to 
> see if the jobs get built.
>
> [1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and 
> https://issues.jenkins-ci.org/browse/JENKINS-25867
> [2] 
> http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
> [3] https://github.com/zaro0508/gearman-plugin-client

Hi Zaro,

Thanks for the reply.

But I updated the gearman plugin to 0.1.2, and used the 
gearman-plugin-client to submit jobs.

# python gear_client.py -s localhost 
--function=build:noop-check-communication

Sat Jul 25 14:16:57 2015
Sending job: build:noop-check-communication to localhost with 
params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid': 
'08ad7a195237493d91eea55789e76128'}

Waiting for jobs to finish.................................


It doesn't work. The job submitted by the client is also pending.

BTW, I cannot see the job submitted by client in my Jenkins GUI. Is that 
correct ?

Thanks.

>
> -Khai
>
> On Thu, Jul 23, 2015 at 9:13 PM, Tang Chen <tangchen at cn.fujitsu.com 
> <mailto:tangchen at cn.fujitsu.com>> wrote:
>
>
>     On 07/24/2015 12:00 PM, Tang Chen wrote:
>
>
>         On 07/24/2015 10:08 AM, Tang Chen wrote:
>
>
>             On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
>
>                 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.
>
>
>             I checked my configuration, and made sure these things:
>             1. I have only a master node, no slave node.
>             2. I have 20 idle executors on master node.
>             3. My master node is online.
>             4. My master node is set to "Utilize this node as much as
>             possible".
>             5. zuul is able to be notified by Gerrit, and tell Jenkins
>             to start jobs.
>
>             But the jobs are always pending.
>
>
>         And my Gearman reports this error sometimes.
>
>         2015-07-25 10:50:44,914 ERROR gear.Server: Exception in poll loop:
>         Traceback (most recent call last):
>           File
>         "/usr/local/lib/python2.7/dist-packages/gear/__init__.py",
>         line 2614, in _doPollLoop
>             self._pollLoop()
>           File
>         "/usr/local/lib/python2.7/dist-packages/gear/__init__.py",
>         line 2626, in _pollLoop
>             ret = self.poll.poll()
>         IOError: [Errno 4] Interrupted system call
>
>         Not sure if it has anything to do with this problem.
>
>         In Jenkins GUI, Gearman connection is tested successfully on
>         127.0.0.1:4730 <http://127.0.0.1:4730>.
>
>
>     Seeing from zuul debug log, Gearman has successfully submitted the
>     jobs.
>
>     2015-07-25 11:42:09,255 DEBUG zuul.Scheduler: Adding trigger
>     event: <TriggerEvent patchset-created openstack-dev/sandbox master
>     205360,1>
>     2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Done adding trigger
>     event: <TriggerEvent patchset-created openstack-dev/sandbox master
>     205360,1>
>     2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Run handler awake
>     2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Fetching trigger event
>     2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Processing trigger
>     event <TriggerEvent patchset-created openstack-dev/sandbox master
>     205360,1>
>     2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
>     Event <TriggerEvent patchset-created openstack-dev/sandbox master
>     205360,1> for change <Change 0x7ff518312c10 205360,1> matched
>     <EventFilter types: patchset-created> in pipeline
>     <IndependentPipelineManager check>
>     2015-07-25 11:42:09,257 INFO zuul.Scheduler: Adding
>     openstack-dev/sandbox, <Change 0x7ff518312c10 205360,1> to
>     <Pipeline check>
>     2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
>     Considering adding change <Change 0x7ff518312c10 205360,1>
>     2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
>     Checking for changes needed by <Change 0x7ff518312c10 205360,1>:
>     2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: 
>      No changes needed
>     2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:
>     Adding change <Change 0x7ff518312c10 205360,1> to queue
>     <ChangeQueue check: openstack-dev/sandbox>
>     2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager:
>     Event <TriggerEvent patchset-created openstack-dev/sandbox master
>     205360,1> for change <Change 0x7ff518312c10 205360,1> matched
>     <EventFilter types: patchset-created> in pipeline
>     <IndependentPipelineManager silent>
>     2015-07-25 11:42:09,258 INFO zuul.Scheduler: Adding
>     openstack-dev/sandbox, <Change 0x7ff518312c10 205360,1> to
>     <Pipeline silent>
>     2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager:
>     Considering adding change <Change 0x7ff518312c10 205360,1>
>     2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager:
>     Unable to find change queue for change <Change 0x7ff518312c10
>     205360,1> in project openstack-dev/sandbox
>     2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager:
>     Starting queue processor: check
>     2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager:
>     Checking for changes needed by <Change 0x7ff518312c10 205360,1>:
>     2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: 
>      No changes needed
>     2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager:
>     Preparing ref for: <Change 0x7ff518312c10 205360,1>
>     2015-07-25 11:42:09,307 INFO zuul.IndependentPipelineManager:
>     Change <Change 0x7ff518312c10 205360,1> depends on changes []
>     2015-07-25 11:42:09,307 DEBUG zuul.MergeClient: Submitting job
>     <gear.Job 0x7ff518325490 handle: None name: merger:merge unique:
>     b425daae0cec4ff3b0d4920ee5533c9c> with data {'items': [{'oldrev':
>     None, 'newrev': None, 'refspec': u'refs/changes/60/205360/1',
>     'merge_mode': 2, 'number': u'205360', 'project':
>     'openstack-dev/sandbox', 'url':
>     'ssh://Fnst@review.openstack.org:29418/openstack-dev/sandbox
>     <http://Fnst@review.openstack.org:29418/openstack-dev/sandbox>',
>     'branch': u'master', 'patchset': u'1', 'ref':
>     'Z81183af13086459d9d9fb8c06af86c09'}]}
>     2015-07-25 11:42:09,308 DEBUG zuul.IndependentPipelineManager:
>     Finished queue processor: check (changed: False)
>     2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager:
>     Starting queue processor: silent
>     2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager:
>     Finished queue processor: silent (changed: False)
>     2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager:
>     Starting queue processor: patch
>     2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager:
>     Finished queue processor: patch (changed: False)
>     2015-07-25 11:42:09,309 DEBUG zuul.Scheduler: Run handler sleeping
>
>     Thanks. :)
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150724/e59158cd/attachment.html>


More information about the OpenStack-dev mailing list