Chromium perf buildbot json file unmanageable ~167K lines so far |
|||||||||
Issue descriptionOur src side buildbot json file is getting large and very unmanageable. It can no longer be loaded in CS or uploaded to rietveld. This means we have to land the CL around the CQ. This file will grow ~100K lines when android is swarmed. The options I see are as follows: 1) auto-generate this file in the recipe instead of checked in 2) split the json into multiple files and have the recipe load multiple? (Is this feasible?) Are there other options? Assigning to stip initially as he was investigating a quick solution on the infra side.
,
Dec 19 2016
There is an owner on this bug, but the status was not "Assigned" or "Started". Fixing. If you do not own this bug, please remove yourself as the owner and make the status "Available".
,
Dec 22 2016
,
Dec 22 2016
,
Jan 5 2017
,
Jan 6 2017
Paweł, I'm punting this to you as per our conversation this morning. We need to figure out how to make these files more manageable and reviewable. I do not like the auto-generate-in-the-recipe idea, that would move us farther back towards the "figure out what to test imperatively" mode of things. I think we should probably split up the file, because I think we should also probably split up chromium.perf; from what I hear, the server is perpetually overloaded regardless. Even ignoring that, though, there's way too much repetition in these files. We need a better way of using macros or something to reduce the duplication.
,
Jan 6 2017
,
Feb 10 2017
,
Jun 30 2017
,
Dec 1 2017
Removing myself from bugs because of team transfer, back to re-triage. See https://goto.google.com/phajdan-goodbye-chrome (Google-internal) and issue 783662 . In case of any questions, feel free to ask - use phajdan@google.com for a faster response. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 Deleted