New issue
Advanced search Search tips

Issue 713985 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 695155
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Lots of "PubSub: WARNING - no build request found for ..."

Project Member Reported by dsansome@chromium.org, Apr 21 2017

Issue description

I'm seeing this error a lot in the master.tryserver.v8 logs.  Why?  Should these build requests be found?  Is it something to be worried about?

https://pantheon.corp.google.com/logs/viewer?project=chrome-infra-logs&minLogLevel=0&expandAll=false&resource=global&logName=projects%2Fchrome-infra-logs%2Flogs%2Fmaster_twistd.log&advancedFilter=resource.type%3D%22global%22%0AlogName%3D%22projects%2Fchrome-infra-logs%2Flogs%2Fmaster_twistd.log%22%0Alabels.%22cloudtail%2Fresource_id%22%3D%22master.tryserver.v8%22&timestamp=2017-04-21T03:50:40.000000000Z

A  [-] PubSub: WARNING - no build request found for 576750 
A  [-] PubSub: Pushing status for builds: [] 
A  [-] PubSub: WARNING - no build request found for 576609 
A  [-] PubSub: Status push timer expired. Pushing updates for: [] 
A  [-] PubSub: WARNING - no build request found for 576744 
A  [-] PubSub: WARNING - no build request found for 576751 
A  [-] PubSub: WARNING - no build request found for 576752 
A  [-] PubSub: WARNING - no build request found for 576749 
A  [-] PubSub: WARNING - no build request found for 576758 
A  [-] URL being requested: POST https://pubsub.googleapis.com/v1/projects/luci-milo/topics/public-buildbot:publish?alt=json 
A  [-] PubSub: WARNING - no build request found for 576748 
A  [-] PubSub: WARNING - no build request found for 576753 
A  [-] PubSub: WARNING - no build request found for 576757 
A  [-] PubSub: WARNING - no build request found for 576756 
A  [-] PubSub: Last send session took total 0.1s, 0.0 load build, 0.0 master, 0.0 send. len_tcq 1. br 15. bs 0 
A  [-] PubSub: WARNING - no build request found for 576754 
A  [-] PubSub: WARNING - no build request found for 576746 
A  [-] PubSub: WARNING - no build request found for 576744 
A  [-] PubSub: WARNING - no build request found for 576751 
A  [-] PubSub: WARNING - no build request found for 576752 
A  [-] PubSub: WARNING - no build request found for 576749 
A  [-] PubSub: WARNING - no build request found for 576758 
A  [-] PubSub: WARNING - no build request found for 576701 
A  [-] PubSub: Scheduling push timer in: 0:00:30 
A  [-] PubSub: WARNING - no build request found for 576570 
A  [-] PubSub: Sending 5424 bytes 
A  [-] PubSub: Send successful: {u'messageIds': [u'108374383152022']} 

 

Comment 1 by hinoka@chromium.org, Apr 22 2017

Status: Assigned (was: Unconfirmed)
This shouldn't happen, but it is.  This could mean one of two things.

A. The build request was consumed but cleaned up
B. The build request was dropped somehow

If this is A. this would be a P2 bug to clean up the loose pointers when the build request is queried but not found.  If this is B, Then this would be a P1 because Milo would be missing actual builds from buildbot.  I haven't seen anything that would indicate (B) is true since all the times I've spot checked the buildbot pending build list equals the milo pending build list, so I'm inclined to believe this is (A).

I'll look into this.
Mergedinto: 695155
Status: Duplicate (was: Assigned)

Sign in to add a comment