Hi Diana,
It is not clear from your description of what is the problem. Could
you elaborate, please?
I have looked at the build history closer and see that this build
configuration depends on libcxx, libcxxabi, libunwind, llvm projects,
and changes to any of these would trigger a build. Depending
Hi Galina,
It seems that our libcxx bots are now triggering builds for any changes to llvm:
http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-aarch64-linux/builds/2434
Should I file a bug report for this?
Thanks,
Diana
On Sat, 19 Oct 2019 at 11:36, Galina Kistanova via cfe-commits
w
Hello everyone,
The staging master is ready to accept bots from the list I have sent
yesterday. Don't wait too long.
The master has been updated and works with both SVN and Github monorepo now.
The following builders are already listening for changes in monorepo and
building monorepo. More are c
On Mon, Oct 14, 2019 at 6:16 PM Galina Kistanova via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Hello everyone,
>
>
>
> We are in the middle of porting the majority of zorg to
> GitHub/monorepo. The following build factories will be ported and if you
> use one of those for your bots, you a
Hello build bot owners!
The staging master is ready. Please feel free to use it to make sure your
bots would work well with the monorepo and github.
The following builders could be configured to build monorepo:
* clang-atom-d525-fedora-rel
* clang-native-arm-lnt-perf
* clang-cmake-armv7-lnt
* cl
Hello everyone,
The build bot is almost ready to move to github.
As the next step we would migrate the staging master to listen for the both
changes, from SVN as it was before, and from github.
Tonight I am going to update the staging (aka silent) master and it will
start working with github.
I
