New issue
Advanced search Search tips

Issue 842771 link

Starred by 1 user
Status: Fixed
Owner:
qyears...@chromium.org
Closed: May 2018
Cc:
no...@chromium.org
mar...@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Buildbucket status 500 responses from pubsub notify handler

Project Member Reported by qyears...@chromium.org, May 14 2018 
Path: /_ah/push-handlers/swarming/notify

Sample error log includes:

   Received message...
   Build id: 8946532931882979744 (.../swarming/swarming.py:1134)
   Build for a swarming task not found yet (.../swarming/swarming.py:1177)
   Task: https://chromium-swarm.appspot.com/task?id=3d787b31a42c6910

Doesn't immediately seem like it's related to bug 842744 (high leasing latency for chromiumos.tryserver), but it's possible?

Comment 1 by qyears...@chromium.org, May 14 2018 

Note, the swarming.py above is:
https://cs.chromium.org/chromium/infra/appengine/cr-buildbucket/swarming/swarming.py?l=1134

It looks like swarming is sending a notify request to buildbucket for a task that's not quite finished yet, and buildbucket is going to retry. I don't think that this is a new thing.

http://shortn/_ZVeHD0tg1w

This seems similar to the issue where swarming sends a pubsub notify to tricium for a task that isn't quite finished yet, so tricium has to check back a few times before the task is finished. I guess this is probably a known issue?

Comment 2 by qyears...@chromium.org, May 15 2018

Status: Fixed (was: Assigned)
This has been resolved by changing the 500s to 400s: https://chromium-review.googlesource.com/c/infra/infra/+/1057987
►

Sign in to add a comment