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

Issue 631132 link

Starred by 1 user
Status: Fixed
Owner:
aga...@chromium.org
Closed: Jul 2016
Cc:
█ benhenry@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

503 errors on tryserver.client.catapult buildbot pages

Project Member Reported by sullivan@chromium.org, Jul 25 2016 
https://build.chromium.org/p/tryserver.client.catapult/

Can the trooper take a look? I'm not sure how long this problem has been ongoing, but I did make some master config changes and do a master restart this morning: https://codereview.chromium.org/2182493002/

Note the uberchromegw links work: https://uberchromegw.corp.google.com/i/tryserver.client.catapult

Comment 1 by aga...@chromium.org, Jul 25 2016

Owner: aga...@chromium.org
Status: Started (was: Untriaged)
Yeah, changing the master_port_alt in that CL is what killed the externally-visible console.

You can:
1) Revert the CL
2) Land a CL to revert just the port change
3) Ask me to change the apache configs to point at the new port

Let me know which you would prefer

Comment 2 by sullivan@chromium.org, Jul 25 2016 

Can you change the apache configs to point at the new port? The buildbot-tool script seems to want the port change, so this is likely to happen again down the road if we revert that part.

Comment 4 by aga...@chromium.org, Jul 25 2016

Status: Fixed (was: Started)
The build.chromium.org page now works.
Project Member

Comment 5 by bugdroid1@chromium.org, Jul 25 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/217c04954546234811dcf35d735e29a195939c6d

commit 217c04954546234811dcf35d735e29a195939c6d
Author: agable <agable@google.com>
Date: Mon Jul 25 20:35:38 2016
►

Sign in to add a comment