Details
Diff Detail
- Build Status
Buildable 31997 Build 31996: arc lint + arc unit
Event Timeline
Cool!
Having a bot for this is great, under these conditions:
- It doesn't send email to regular contributors when it goes red (it can email you and me and others who'd like to opt in)
- It doesn't show up on http://lab.llvm.org:8011/console
Basically, it needs to be consistent with the 1st paragraph at https://github.com/llvm/llvm-project/blob/master/llvm/utils/gn/README.rst
From what I understand, this doesn't add a bot yet, so lgtm.
zorg/buildbot/builders/sanitizers/buildbot_gn.sh | ||
---|---|---|
30 | What's the motivation for doing a stage 1 build with cmake first? (Not saying it's wrong and you can keep it if you want, just trying to understand the motivation.) If you just want some clang binary as host compiler, you could alternatively git clone https://chromium.googlesource.com/chromium/src/tools/clang and then run update.py -- this will download a prebuilt clang and lld, and will be much faster than building it from scratch. If you want to test bootstrap builds, I think there's a way to hold the GN build so that it does a bootstrap build in a single build dir. | |
39 | Does the binary downloaded by llvm/utils/gn/get.py not work on this bot? | |
56 | You don't need to pass use_lld=true is_optimized=true is_debug=false -- use_lld defaults to true if clang_base_path is set, and optimized release builds (with asserts) is the default . |
already done in D61965, but you need to opt-in. I can do it for you if you don'e have zorg checkout.
- It doesn't show up on http://lab.llvm.org:8011/console
not done yet, as-is it will probably will show in sanitizers section. I'll check how to avoid that.
Basically, it needs to be consistent with the 1st paragraph at https://github.com/llvm/llvm-project/blob/master/llvm/utils/gn/README.rst
From what I understand, this doesn't add a bot yet, so lgtm.
Empty bot is added in D61965 but it will show up only after master restart. My plan is to land this patch only after empty one is alive, as .sh scripts do not need master restart and will be used by bots immediately.
Don't hardcode default GN options
zorg/buildbot/builders/sanitizers/buildbot_gn.sh | ||
---|---|---|
30 | That's for historical reasons. We need working clang on the host which is newer than provided by distro. Also current setup let us quickly switch to the just commited into upstream fix or feature if needed. But I don't remember we used that. So we have other bots which use the same build_stage1_clang_at_revison functions, which is on cmake and we even can switch to GN, but it does not realy matter. We just need some fresh clang. build_stage1_clang_at_revison use fixed revision which we update manually couple times a year. We can switch to prebuilt binaries e.g. from chrome, but this build happens only once per bot restart which is usually just a couple times a day. So at average it does not bother us yet. But we open to switching to prebuild clang. | |
39 | It does not. depo_tools version does not work as well. |
What's the motivation for doing a stage 1 build with cmake first? (Not saying it's wrong and you can keep it if you want, just trying to understand the motivation.)
If you just want some clang binary as host compiler, you could alternatively git clone https://chromium.googlesource.com/chromium/src/tools/clang and then run update.py -- this will download a prebuilt clang and lld, and will be much faster than building it from scratch.
If you want to test bootstrap builds, I think there's a way to hold the GN build so that it does a bootstrap build in a single build dir.