This was last changed in:

https://chrome-internal-review.googlesource.com/c/chrome-golo/chrome-golo/+/631077
and
https://chrome-internal-review.googlesource.com/c/chrome-golo/chrome-golo/+/631227

There was a fix of some sort, and then a revert with no message.  friedman can you take a look?

What are the actual URLs to these files?

This should really be moved off of master1 (or any master) as it's fate is doomed in a LUCI world and we really don't want to implement a lot of bubblegum fixes to continue hosting it in this manner.

master.chromium wasn't running.

I manually started it and got: hzl,jbudorick

looks like master manager or something else stopped the master.

Please move this service off master1 if you care about it.

That's an interesting dependency.  I thought apache2 would've been responsible for serving static files off a server.  How wrong I was.

master.chromium has been migrated to LUCI.  I'll keep a skeleton of the former buildbot master running for the rotation json.

I think the SoM team inherited this service, so from there, I'll leave it to them to decide what to do with it.

Well, yes, apache2 does serve this static file, but it was "bundled" with master.chromium in some kind of parasitic way.  Now that the host has finally died, the parasite is no longer with us, only if we put the host on some kind of life support will it work.

We could host this on a fake master for the time being as well (port 80 or so) but it would be yet another hack to keep doing "the wrong thing".  I'm sure I can work something out temporarily, but if this is a required component of anyone's workflow, I'd rather see it moved somewhere much more appropriate.

If we boot master.chromium back up, is that sufficient to keep things alive for a few weeks or a month, while the devx folks (hopefully) make this all obsolete?

+ olakar who's working on deprecating the rotation script. Ola's on a long vacation, which delayed the timeline on this project a bit. 

I think a month would be tight for our initial plans, but if we need to turn down master.chromium soon, we should do a shorter term migration where we move these scripts onto App Engine as is. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/3ac6a75085c7c1749f5c1126f8accf2ce1827eec

commit 3ac6a75085c7c1749f5c1126f8accf2ce1827eec
Author: Ryan Tseng <hinoka@google.com>
Date: Thu Jun 21 21:22:16 2018

Remove builders from master.chromium

This keeps a skeleton of master.chromium up and running
so that the rotation json still works.

Bug:  855093 
Change-Id: I77374dd48d4d3ba7e7ee459d7a1b96e23a3ce432
Reviewed-on: https://chromium-review.googlesource.com/1110451
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>

[delete] https://crrev.com/37988a45079d1f26366657ff5d0d4e720233fad9/masters/master.chromium/master_full_cfg.py
[delete] https://crrev.com/37988a45079d1f26366657ff5d0d4e720233fad9/masters/master.chromium/master_source_cfg.py
[modify] https://crrev.com/3ac6a75085c7c1749f5c1126f8accf2ce1827eec/tests/masters_recipes_test.py
[modify] https://crrev.com/3ac6a75085c7c1749f5c1126f8accf2ce1827eec/masters/master.chromium/slaves.cfg
[modify] https://crrev.com/3ac6a75085c7c1749f5c1126f8accf2ce1827eec/masters/master.chromium/master.cfg

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/puppet/+/0315ed26fe52c1c5ed30fe545e78c4aa00b6005d

commit 0315ed26fe52c1c5ed30fe545e78c4aa00b6005d
Author: Elliott Friedman <friedman@google.com>
Date: Fri Jun 22 21:20:32 2018

Based on all the error emails:

https://groups.google.com/a/google.com/d/topic/chrome-troopers/KuUXmwlQBFU/discussion

I think something is still not working right.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/f066acc2d15fd62e43e3e52c28d481cd8b6f63b0

commit f066acc2d15fd62e43e3e52c28d481cd8b6f63b0
Author: Ryan Tseng <hinoka@google.com>
Date: Mon Jun 25 18:43:14 2018

Adding Milestone for SoM bug triage. 

I think this is fixed now? Please reopen if not.