New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 876989 link

Starred by 1 user
Status: Closed
Owner: ----
Closed: Aug 24
Cc:
█ amineer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Chromium Dash - Chromeperf: 405: API request denied.

Project Member Reported by petermarshall@chromium.org, Aug 23 
I open this page: https://chromiumdash-staging.googleplex.com/commit/54a59e001bc39dfa9e52b60e91d5b72c96118e73 while logged in to my chromium account. 

Down the bottom an error popup appears - "Chromeperf: 405: API request denied."

In the console:

Failed to load https://chromeperf.appspot.com/api/alerts?max_start_revision=55315&min_end_revision=55315&limit=5000: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://chromiumdash-staging.googleplex.com' is therefore not allowed access. The response had HTTP status code 500.

Comment 1 by prasadv@google.com, Aug 23 

Thank you so much for reporting this, may I know any reason why Chromium Dash staging instance is used instead of production instance.
https://chromiumdash.appspot.com/commit/54a59e001bc39dfa9e52b60e91d5b72c96118e73 works fine on production instance for me.
Can you please use the production instance https://chromiumdash.appspot.com, and see if it works for you.

Please note that Chromium Dash staging instance is only for testing the ongoing development and might not be reliable to use.

Comment 2 by petermarshall@chromium.org, Aug 24

Status: Closed (was: Unassigned)
Thanks, it works fine on non-staging. I was using staging for ages because there were features that had not been moved to production e.g. the links to chromperf for the roll of a commit.
►

Sign in to add a comment