+infra people.
OK - the new master is up and running here: https://build.chromium.org/p/chromium.memory.full/console.
I guess the next step is to put up a patch into the infra repo which:
1. grabs all the slaves from the .fyi master and makes the .fyi slaves fakes
2. points the main waterfall page at .full
And then ask for both masters to be restarted. Does that sound right?
Gads, this didn't go well. Sorry all for landing the change on Friday, that wasn't a good idea.
Current status is that there are still some problems:
1. the main waterfall page doesn't show the new master's build statuses. This appears to be due to some appengine thing not doing what it should, I suspect something needs to be restarted.
2. all the builds on the new master are failing. It looks like there are a few things at play:
- some builds are maybe genuinely broken
- uploading builds is failing because some remote endpoint (bucket) doesn't appear to be there. This could be the same underlying cause as problem 1.
3. the label is incorrect on the main waterfall. This is easy to fix but lowest priority, the link points to the right thing.
With help from chrishall@ and dsansome@ we're getting to the bottom of the problems -
1. The appengine app chromium_build had some hardcoded paths. A change is in the process of landing to fix these. This will need to be manually deployed but we have instructions on how to do this
2. Haven't looked at the genuine-looking problem yet. The upload problem was because the Google Storage bucket didn't exist. chrishall@ has created one but we're now getting permission errors
3. A fix has landed for this :)
Further update:
chrishall@ has managed to restart the chromium_build app. In the process we discovered you need to navigate to a /tasks/fetch_pages URL which does some caching.
Current status:
1. Main waterfall page has all the bits it should
2. Linux TSan builds are working and green
3. MSan builds had a build problem due to a mojo change, that has been reverted. Linux MSan built successfully and tests are running, ChromeOS MSan build is in progress
4. DrMemory bots needed a different Google Store setup (gs://chromium.memory.full vs gs://chromium.memory.full.archive for the other builders). That has been created now by chrishall@. Hopefully the required permissions setup matches the other store as this all needs to be done manually. There has also been a compile failure on the DrMemory bots which together with the long cycle time makes it hard to get this operational.
It looks like the chromium.memory.fyi master configs are still in the build repo. Can I delete them at this point? I'll send a CL since I suspect we can.
Comment 1 by bugdroid1@chromium.org
, Jun 2 2016