Buildbot now up and new build failures

I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall
It builds every single revision of llvm, runs the testsuite, and
reports the results. It takes about 3 minutes per build+test right
now (it's an 8 core machine).

Currently i have it building x86_64-linux.
Setting up a builder/slave for any platform would be trivial.
I simply don't have machines running anything but x86_64-linux that i
can use for this purpose.

It simply requires installing buildbot , and pointing it at this
buildbot as it's master.
You only need to be able to connect to the outside world, you don't
have to be able to receive connections.
Let me know if you have a machine/platform you want to connect to this
as a build slave and i can walk you through it.

It can also test patches for you and give you the results (currently
this requires buildbot be installed on your machine, i will make it
web/email accessible)

I will add the dejagnu logs to the clickable links, as well as make it
link to just the list of FAIL's so you don't have to search the log.

I will also make it bootstrap llvm-gcc once or twice a day.
--Dan

This is great stuff. Thanks Daniel.

Evan

Hi Daniel,

I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall
It builds every single revision of llvm, runs the testsuite, and
reports the results. It takes about 3 minutes per build+test right
now (it's an 8 core machine).

how does it report the results? Can it email the mailing list if the
build fails for example?

Ciao,

Duncan.

Hi Daniel,

I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall
It builds every single revision of llvm, runs the testsuite, and
reports the results. It takes about 3 minutes per build+test right
now (it's an 8 core machine).

how does it report the results? Can it email the mailing list if the
build fails for example?

It can, it could also email the list only if it goes from success to
failure (so that continual failures don't generate an email each),
etc.

I haven't set up the email notifier yet, i am still getting it to add
the test result links nicely first, then i'll get the email notifier
added.

(It's a matter of a few lines of config :P)

Thanks. But please send the build notifications to llvm-testresults@cs.uiuc.edu instead.
Evan

It will send them to llvm-testresults and the person who caused the failures :slight_smile:

Daniel,

Thanks! Is this doing a build of Ada and Fortran? :slight_smile:

-bw

No :slight_smile:

I'm trying to start by having something that keeps people from
breaking the build and tests (by letting them submit patches and being
whiny 3 minutes after something breaks).
Once that is done, we can move to something that keeps all the
languages in good shape.

I think if i simply made it do everything at once, people would just
ignore it. At least, that's my experience :slight_smile:

I'm happy to have people edit the config files the master uses to tell
the slaves what to do in terms of building/etc

I'd like to volunteer a Windows build slave, building via Visual
Studio (or CMake->VS) as that's the configuration I care about. Is
that plausible?

Before worrying about the buildbot part, I suppose I need to be able
run the tests. Do people do that regularly on Windows? It seems the
makefiles depend on running configure, but perhaps some (scary) hybrid
of building via VS, and running 'make check' under devilspawn^Hcygwin
is possible?

scott

That's cool. And I agree that it if didn't work, people would ignore
it. :slight_smile: At the moment, we have only Duncan and a couple of Fortran
guys to tell us when an Apple merge has broken something. I'm sure
that they would welcome an early detection system. :slight_smile:

-bw

I set up a buildbot for llvm at http://google1.osuosl.org:8011/waterfall
It builds every single revision of llvm, runs the testsuite, and
reports the results. It takes about 3 minutes per build+test right
now (it's an 8 core machine).

Currently i have it building x86_64-linux.
Setting up a builder/slave for any platform would be trivial.

I'd like to volunteer a Windows build slave, building via Visual
Studio (or CMake->VS) as that's the configuration I care about. Is
that plausible?

If you can build it via a series of repeatable steps, it should be doable.
You can have different build steps for different builders/platforms if
you want, so for win32 we could do whatever is necessary to make it
run there.

That's cool. And I agree that it if didn't work, people would ignore
it. :slight_smile: At the moment, we have only Duncan and a couple of Fortran
guys to tell us when an Apple merge has broken something. I'm sure
that they would welcome an early detection system. :slight_smile:

My tester builds Ada and Fortran llvm-gcc nightly on x86-32,
and Fortran nightly on x86-64 (Ada doesn't build on x86-64
due to a regalloc bug, PR2556 :frowning: ). At some point it would
be nice to have the buildbot build Fortran since (1) this is
easy to do (no special requirements), and (2) hopefully Fortran
will be part of the next release.

Ciao,

Duncan.

Hi Daniel,

I see that you're doing a Debug build. Could you do a "Release" or
"Release-Asserts" build instead? This will catch errors which
developers won't normally see.

-bw

Hi Daniel,

I see that you're doing a Debug build. Could you do a "Release" or
"Release-Asserts" build instead? This will catch errors which
developers won't normally see.

I never knew about buildbot until just now.

This could really help with the validation proposal I just posted. Can
buildbot aggregate results from builds on various machines (.e.g each machine
building and testing a different codegen target) and send reports through
e-mail?

                                                  -Dave

Yes.

Yes.

Cool. I'd like to look at installing something here. You offered to walk us
through how to do this.

I'll see if I can install buildbot here and then mail you back when I'm ready
to go.

                                                     -Dave

Ok, I've got buildbot installed on a machine here. What's next?

Feel free to e-mail me privately.

                                               -Dave