New issue
Advanced search Search tips

Issue 819144 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 818705



Sign in to add a comment

HTTP 500 error when trying to manually start a bisect

Project Member Reported by rmcilroy@chromium.org, Mar 6 2018

Issue description

I'm getting 500 HTTP errors when I try to start a bisect on the chromeperf dashboard (e.g, [1] and [2]).

When I click the bisect button I get the following errors in the console:
  Failed to load resource: the server responded with a status of 500 ()
  simple_xhr.html:65 POST 
  https://chromeperf.appspot.com/pinpoint/new/bisect 500 ()
    send	@	simple_xhr.html:65
    Promise	@	simple_xhr.html:71
    asPromise	@	simple_xhr.html:70
    onCreateJob	@	pinpoint-job-dialog.html:154
    handler	@	polymer.html:507


[1] https://chromeperf.appspot.com/group_report?bug_id=818707
[2] https://chromeperf.appspot.com/group_report?bug_id=818695
 
Cc: hablich@chromium.org
Blocking: 818705

Comment 3 by dtu@chromium.org, Mar 6 2018

Thanks for the report! I've deployed a fix:
https://chromium-review.googlesource.com/c/catapult/+/951884

Comment 4 by dtu@chromium.org, Mar 6 2018

Owner: dtu@chromium.org
Status: Fixed (was: Untriaged)

Sign in to add a comment