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

Issue 738271 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Fetch tests from build functionality returns error

Project Member Reported by haddowk@chromium.org, Jun 30 2017

Issue description


Enter a build and test name and click the "Fetch tests from build" UI returns an error 0

Confirmed on cautotest also,  so far nothing useful from the logs.

https://screenshot.googleplex.com/8fpVCQO8jUO
 

Comment 1 by dshi@chromium.org, Jun 30 2017

I just tried veyron_mighty-release/R61-9695.0.0 in cautotest, it works fine. 

When you see the error, what's the stacktrace? (click the button at the end of the page for detailed output). Likely some devserver load issue?
Yeah I can not repo on cautotest

Moblab stacktrace is not too helpful

Received error 500 
status: 500
date: Fri, 30 Jun 2017 05:47:16 GMT
server: Apache
content-length: 593
content-type: text/html; charset=iso-8859-1


<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at 
 [no address given] to inform them of the time this error occurred,
 and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<hr>
<address>Apache Server at 100.96.48.76 Port 80</address>
</body></html>

------------------------------
Failed to update tests for given build.
Status: WontFix (was: Untriaged)

Sign in to add a comment