[LLVMdev] Plans for the Apple supported Darwin buildbot cluster

Chris Matthews chris.matthews at apple.com
Tue Dec 2 14:27:12 PST 2014


Committed in r223163.

Thanks David!

> On Dec 2, 2014, at 1:40 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
> 
> Hi Chris,
> 
> I seem to have missed the phabricator emails - sorry about that.  I might have time to commit it tomorrow afternoon (UK time), or at the weekend if not, but I'm very happy if you want to get there first.
> 
> David
> 
> On 2 Dec 2014, at 21:32, Chris Matthews <chris.matthews at apple.com> wrote:
> 
>> David, I like your patch. I applied the feedback in Phabricator and tested internally.  Is it your intent to contribute the patch?  I could commit the revised version on your behalf?
>> 
>>> On Aug 14, 2014, at 2:41 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
>>> 
>>> I've put the diff in Phabricator here:
>>> 
>>> http://reviews.llvm.org/D4901
>>> 
>>> If you think it looks vaguely sensible then let me know and I'll commit it.
>>> 
>>> David
>>> 
>>> On 13 Aug 2014, at 16:37, Chris Matthews <chris.matthews at apple.com> wrote:
>>> 
>>>> Yes! That would be really great! 
>>>> 
>>>>> On Aug 13, 2014, at 3:09 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote:
>>>>> 
>>>>>> On 12 Aug 2014, at 19:34, Chris Matthews <chris.matthews at apple.com> wrote:
>>>>>> 
>>>>>> The most notable change will be a switch from Buildbot to Jenkins.
>>>>> 
>>>>> We're currently running LLVM test builds in Jenkins and I have patched lit to produce JUnit XML output that Jenkins can consume (it's not pretty, but it does at least let you produce the graphs of tests / failures for each build).  If there's general interest in this feature, I'd be happy to upstream it.  The current implementation writes the JUnit XML to a file specified on the command line, so you also get the normal output.  It could be improved, but it's probably a sensible starting point for anyone wanting to work on this.
>>>>> 
>>>>> David
>>>>> 
>>> 
>> 
> 





More information about the llvm-dev mailing list