Hello David, Thank you very much for your clarifications. They are very helpful. Sorry for the delay in answering your message.
David Spickett <david.spick...@linaro.org> writes: >> There was a big impact on the flang builds on tcwg-jade-01 (which went from >> 1h–2h to >> 10min–30min), but not on other builds. > > Given how much resource flang takes up this is a great result even if > they're the only faster builds. That's good to know. I've been looking at the “build times” graph for other builds and they haven't changed much since July 6th (when I changed the cache sizes). >> Since different machines have different disk sizes and free space I chose >> different >> ccache max sizes for them, as follows: > > Can you document how you set, and why you chose, the sizes? There is a > bit about ccache at the end of > https://linaro.atlassian.net/wiki/spaces/TCWG/pages/22343946024/LLVM+Docker+Buildbot+Maintenance > you could put it there. Thanks for the suggestion. I expanded that section with the information I gathered and the changes I made. Please let me know if there's anything I can improve on it. Since the libc++ buildkites share the ccache configuration with the LLVM buildbots, I briefly mentioned that (with a link to the LLVM buildbot page) at https://linaro.atlassian.net/wiki/spaces/TCWG/pages/22405546190/Buildkite+Bot+Maintenance > Particularly want to know if this config must be set each time or is > automated. I *think* the volumes are made by hand but I didn't confirm > that. I guess the cache size is set inside each container but must > agree between the ones that share a ccache volume? The config is stored in ~tcwg-buildbot/.ccache/ccache.conf. Since the shared ccache volume is mounted at ~tcwg-buildbot/.ccache, the cache size can be set manually once (either by editing the ccache.conf file or with “ccache --max-size SIZE”) and will be persisted and shared across containers that share the a ccache volume. I added this information to the wiki. Please let me know if it should be clarified or expanded. I also believe that the volumes are made by hand, but I didn't confirm that either. I didn't find anything in the dockerfiles scripts to create these volumes. >> * The following tcwg-llvmbot_tk1-* machines are currently unreachable so I >> couldn't >> examine them: >> * The following tcwg-llvmbot_tk1-* machines are running an llvmbot container >> but no >> builder container, so I didn't change their ccache configuration: > > For a while we only had 3/4 actually working which is why you see some > "pretending" to be someone else. It is expected that the ones that are > back online now aren't doing anything. Ah, makes sense. Thanks for the information. >> * Going through our ssh config file I didn't find these build bots that >> are listed at http://llvm.validation.linaro.org/ so I didn't check >> their ccache usage: > >> - clang-arm64-windows-msvc-2stage >> - clang-arm64-windows-msvc >> - clang-arm64-windows-msvc-2stage >> - clang-arm64-windows-msvc > > These run on the surface laptops > (https://linaro.atlassian.net/wiki/spaces/TCWG/pages/22395192116/Accessing+Windows+on+Arm+machines). > > These do not use ccache at this time (no mention on > https://linaro.atlassian.net/wiki/spaces/TCWGPUB/pages/25310167965/How+to+setup+LLVM+buildbots+for+Windows+on+Arm). Ok. > > - clang-native-arm-lnt-perf > > - clang-armv7-vfpv3-full-2stage > > - clang-thumbv7-full-2stage > > This is another case where the "builder" name (builder meaning the > configuration it builds) is served by a "worker" that has a different > name. So lnt-perf runs on whatever is running the tk1-02 container > (https://lab.llvm.org/buildbot/#/builders/113). > > The other 2 are on the "silent" buildmaster, for example > https://lab.llvm.org/staging/#/builders/169. Thanks for the clarifications. > The current layout for the tk1s I wrote out in > https://git.linaro.org/toolchain/jenkins-scripts.git/commit/?id=e54ac9c17326434abd2d3aa66269cafaa3a6174b. > And yeah, it makes little sense but we can unpick it now we've got > some more nodes online. > (short term it is easier to move containers around on our end than > change the llvm side config) Ah, that is a very informative commit. Thanks for pointing it out. > > - libcxx aarch64 > > - libcxx aarch64 -fno-exceptions > > jade-04 runs 2 AArch64 buildkite agents that can build either of these > configs depending on who picks it up first. So that might have made it > less obvious. > > Or these are references to the pre-buildkite buildbot libcxx bots but > I'm pretty sure our monitoring is up to date and wouldn't include > them. Thank you again for providing this information! -- Thiago _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
