rietveld sluggish recently |
||||||||||
Issue descriptionrietveld seems quite sluggish recently, we were discussing it on IRC and wondered how rietveld queries trybots to see if any try jobs have run? A random theory - Could this be how rietveld queries for try jobs run, if it is asking every server for results perhaps the increase in trybots could result in a decrease in performance. I only thought this because once yesterday I got an error on my patchset that it couldn't query the try jobs. If so, perhaps we could have a bit on the codereview patchset that determines whether any try jobs have ever been run, this would avoid having to query any try servers. ofc, if my theory is off base then feel free to close ticket or point me at other investigation work going on as to the sluggishness.
,
May 4 2016
There was an issue with cloud endpoints. It affected many chrome infra services, fixed yesterday. I'll check if it is still a problem
,
May 5 2016
It is still an issue, and still on the Cloud Endpoints side.
,
Jun 21 2016
,
Jun 21 2016
,
Jun 27 2016
,
Jun 27 2016
,
Jan 18 2017
Pri-3 that hasn't been updated in 180+ days with status=assigned or started? Get real. I've unassigned you and marked this available. If you're truly working on this, update the priority and reassign yourself or someone who is working on this.
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2018
Rieveld has been turned read-only 1 year ago. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by jrobbins@chromium.org
, May 4 2016