The buidlbot builds the translation_unit clang tool, along with all of clang, on each build step, which is a lot of wasted time.
Either it should do incremental builds, or perhaps even better download a prebuilt binary of the tool.
FWIW, I know update.py isn't really meant for development--it's more for packaging clang builds--but in practice, it's quite useful for iterating on the clang plugins. People who hack on the plugins have mostly been doing ninja -C third_party/llvm-build/Release+Asserts, but it would be kind of nice if update.py had an incremental mode.
Also, are builders for a given bot dedicated? Or can they be shared among several different builders?
> it would be kind of nice if update.py had an incremental mode.
It used to be incremental actually. It seems this buildbot just nukes the build directory each time. And it seems also our script has become non-incremental(?), maybe because we clear the cmake cache too hard.
> Also, are builders for a given bot dedicated? Or can they be shared among several different builders?
If I understand the question correctly, no machines don't need to be dedicated to a specific buildbot. Machines can be shared by multiple buildbots.
In this case it seems that the buildbot is using a dedicated VM, though.
Our goal is to have a dedicated VM per configuration (linux, android, windows, and so on). Eventually, we'll likely have more than one slave per config as we try to speed up the generation of Xrefs.
Comment 1 by h...@chromium.org
, May 19 2017