1061284 - api/project/mozilla-central/resultset/ returning ISE 500

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P1)

Description

[Ed Morley [:emorley]]

1) Open http://treeherder-dev.allizom.org/ui/#/jobs?repo=mozilla-central&revision=1db35d2c9a2f
2) Open web console & wait a few mins

Later API calls return 500s (not the ones on initial pageload):

GET http://treeherder-dev.allizom.org/api/project/mozilla-central/resultset/ [HTTP/1.1 500 INTERNAL SERVER ERROR 193ms]

http://treeherder-dev.allizom.org/api/project/mozilla-central/resultset/?count=1&format=json&full=true&id__in=462&offset=0&revision=1db35d2c9a2f&with_jobs=true

Comment 1

[Jonathan Eads ( :jeads )]

edmorley, the urls provided are pointed at the treeherder development server (http://treeherder-dev.allizom.org). When I replace with the production host, https://treeherder.mozilla.org, in the url provided:

https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-central&revision=1db35d2c9a2f

Later API calls do not seem to be returning 500s after initial pageload and also after several minutes on the page. Maybe the wires got crossed on dev for awhile?

Can you try reproducing this on production?

Comment 2

[Ed Morley [:emorley]]

Yeah I know the comment 0 link is dev - I was checking the recently landed but not pushed to prod changes hadn't broken anything :-)

This still repros on dev for me on, but doesn't on prod. If this is only a glitch in the dev DB then fair enough, however if it's due to recently landed changes then we need to figure it out before we deploy the next batch.

Note you need to wait ~2 mins, and another 500 occurs every 2 mins after that (guessing UI refresh?).

Comment 3

[Jonathan Eads ( :jeads )]

AutomatedTester ran into this on production. You can reproduce with this url

https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=8352094a1452

Comment 4

[Jonathan Eads ( :jeads )]

This bug was fixed in https://github.com/mozilla/treeherder-service/pull/201