search for: greenbot

Displaying 9 results from an estimated 9 matches for "greenbot".

2019 Oct 18
2
[Openmp-dev] [cfe-dev] RFC: End-to-end testing
Renato Golin <rengolin at gmail.com> writes: > On Thu, 17 Oct 2019 at 18:10, David Greene <greened at obbligato.org> wrote: >> From other discussion, it sounds like at least some people are open to >> asm tests under clang. I think that should be fine. But there are >> probably other kinds of end-to-end tests that should not live under >> clang. > >
2015 Oct 07
2
Buildbot Noise
One strategy I use for our flaky bots is to have them email me only. If the failure is real, then I forward the email to who ever I find on the blame list. For a flaky build, this is least you can do. For our flaky builds I know how and why they are flaky, some person that gets email does not. This is also a great motivator to help me know what is wrong, and how to fix it. By default, all new
2015 Oct 13
2
RFC: Introducing an LLVM Community Code of Conduct
...eat work before, so I take this > more as her personal merit than anything else. > > Since we're delving into this topic... > > I expected the foundation to own and improve the validation > infrastructure, and the web presence. So far I only saw Apple building > the great GreenBot, but when I wanted to help, it seemed this would be > something between me and on Apple employee. > > I also saw the migration to a new server (thanks again Tanya), but > that's very far from providing a stable infrastructure. If Tanya is > the only one doing things, of course s...
2015 Oct 13
3
RFC: Introducing an LLVM Community Code of Conduct
On Tue, Oct 13, 2015 at 4:55 AM David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 13 Oct 2015, at 02:42, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > If you have questions, please see feel free to contact the LLVM > Foundation Code of Conduct Advisory Committee by emailing conduct at llvm.org > . > > My main
2019 Oct 10
3
[cfe-dev] RFC: End-to-end testing
Renato Golin via cfe-dev <cfe-dev at lists.llvm.org> writes: > I'd recommend trying to move any e2e tests into the test-suite and > make it easier to run, and leave specific tests only in the repo (to > guarantee independence of components). That would be a shame. Where is test-suite run right now? Are there bots? How are regressions reported? > The last thing we want
2015 Oct 07
2
Buildbot Noise
...ed revision, and >> trigger most other builds from those. > > This would be the perfect world. We should move towards getting this setup then. There is some code that needs to be setup in buildbot, as well as an agreement on what gets attached to what. > > When Apple moved to GreenBots, I was expecting that we'd be moving too > not long after. I was also expecting the LLVM Foundation to be driving > this change, and I'd have dived head first to have what you have. > > But it makes no sense for me to do that on my own, locally. Nor I have > bandwidth or re...
2015 Oct 14
4
RFC: Introducing an LLVM Community Code of Conduct
...this >> more as her personal merit than anything else. >> >> Since we're delving into this topic... >> >> I expected the foundation to own and improve the validation >> infrastructure, and the web presence. So far I only saw Apple building >> the great GreenBot, but when I wanted to help, it seemed this would be >> something between me and on Apple employee. >> >> I also saw the migration to a new server (thanks again Tanya), but >> that's very far from providing a stable infrastructure. If Tanya is >> the only one doing...
2015 Oct 07
2
Buildbot Noise
On 7 October 2015 at 22:44, Eric Christopher <echristo at gmail.com> wrote: > I think this is a poor analogy. You're also ignoring the solution I gave you > in my previous mail for slow bots. I'm not ignoring it, I'm acting upon it. But it takes time. I don't have infinite resources. > If you can't give some basic stability guarantees then the bot > is only
2015 Oct 01
8
Buildbot Noise
...r all these adjustments, we'll need some form of walk-back on the history to find the previous genuine result, and we'll need to mark results with some metadata. This may involve some patches to buildbot. 2.3 Detecting fixed bots Another interesting feature, that is present in the "GreenBot" is a warning when a bot you broke was fixed. That, per se, is not a good idea if the noise levels are high, since this will probably double it. So, this feature can only be introduced *after* we've done the clean ups above. But once it's clean, having a "green" email will p...