[LLVMdev] Validation Update
Tanya M. Lattner
tonic at nondot.org
Thu Nov 20 14:19:08 PST 2008
> Right now the buildbot is set up to build every N commits (N=10 for testing
> purposes) and also build every Sunday at midnight. The buildbot does not
> automatically tag successful validations. That will take some more work and
> we don't want that automation quite yet anyway. We'll do it manually for a
> while and then once we get the gist of it we can make it automatic.
How exactly do you plan to validate it? What point of reference will you
be using as a start?
> One thing that would be nice to have is a commit hook on trunk (and eventually
> release branches) that lets buildbot know when changes are submitted. As of
> now, buildbot polls the svn server every 10 minutes, meaning it could miss
> one of the "every 10" commits (revision mod 10 == 0). The buildbot manual
> talks a bit about what the svn server needs to do here:
>
> http://buildbot.net/repos/release/docs/buildbot.html#PBChangeSource
>
> Could we get that set up in the llvm.org svn commit hook?
What are the pros and cons of this? How much does it tax the server?
> Eventually we'll want to migrate the buidlbot master to some publicly
> accessible machine so others can contribute machines to do validations (for
> various architectures, etc.). Where should this get hosted? Hosting at
> llvm.org would be great but I'm not sure that's possible. Daniel has a
> machine set up so that's a possibility too. Wherever it goes, I'll need an
> account so I can muck around with the buildbot config as build machines are
> added, targets change, etc. Eventually that account should migrate to
> whomever is the overall validation coordinator (in the proposal I volunteered
> myself to play that role for now).
The LLVM server is not the place to host this. Could Cray host a machine
to do this?
-Tanya
>
> -Dave
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
More information about the llvm-dev
mailing list