As seen on this CR, the post-merge job has not run. It seems to be configured, and looks correct to me. Also note the same post-merge job was running fine on other projects (but I have not checked if that's still the case).
The same issue is happening for WDQS, so I'm assuming this is a more general problem, at least happening for all maven based search projects.
The change got merged on 03/18 at 09:29 UTC. From Zuul debug logs
2019-03-18 09:29:11,764 DEBUG zuul.source.Gerrit: Updating <Change 0x7fd138877a90 496361,4>: change is merged 2019-03-18 09:29:11,765 DEBUG zuul.Scheduler: Adding trigger event: <TriggerEvent change-merged search/glent master 496361,4> 2019-03-18 09:29:11,765 DEBUG zuul.Scheduler: Done adding trigger event: <TriggerEvent change-merged search/glent master 496361,4>
And in the main event loop:
2019-03-18 09:29:11,766 DEBUG zuul.Scheduler: Processing trigger event <TriggerEvent change-merged search/glent master 496361,4> ... 2019-03-18 09:29:11,768 DEBUG zuul.IndependentPipelineManager: Starting queue processor: postmerge 2019-03-18 09:29:11,768 DEBUG zuul.IndependentPipelineManager: Finished queue processor: postmerge (changed: False)
For some unknown reason, the event has not been accepted by the postmerge pipeline :-(
I have added it manually with zuul enqueue CLI utility on contint1001:
2019-03-18 10:14:42,715 DEBUG zuul.IndependentPipelineManager: Starting queue processor: postmerge
2019-03-18 10:14:42,715 DEBUG zuul.IndependentPipelineManager: Checking for changes needed by <Change 0x7fd138877a90 496361,4>:
2019-03-18 10:14:42,715 DEBUG zuul.IndependentPipelineManager: No changes needed
2019-03-18 10:14:42,715 DEBUG zuul.IndependentPipelineManager: Preparing ref for: <Change 0x7fd138877a90 496361,4>
2019-03-18 10:14:42,715 INFO zuul.IndependentPipelineManager: Change <Change 0x7fd138877a90 496361,4> depends on changes []
2019-03-18 10:14:42,716 DEBUG zuul.MergeClient: Submitting job <gear.Job 0x7fd1331cc2d0 handle: None name: merger:merge unique: 99d498b4aac54e37beb91a5fbf6c3a2f> with data {'items': [{'oldrev': None, 'newrev': None, 'refspec': u'refs/changes/61/496361/4', 'merge_mode': 2, 'number': '496361', 'connection_name': 'gerrit', 'project': 'search/glent', 'url': 'ssh://jenkins-bot@gerrit.wikimedia.org:29418/search/glent', 'branch': u'master', 'patchset': 4, 'ref': 'Z904fb1fed77e4b2797e306e1ff2151eb'}]}
2019-03-18 10:14:42,717 DEBUG zuul.IndependentPipelineManager: Finished queue processor: postmerge (changed: False)I have no idea why it did not get accepted in the first place :-(
That got raised today as well for operations/mediawiki-config , I have no idea about the root cause though :-/ I guess I should have investigated earlier.
Anyway, marking as a duplicate of T219017 which has a lot more details.
I have added it manually with zuul enqueue CLI utility on contint1001
Note, when manually adding changes with zuul enqueue the event filters are not processed at all.