teemperor added a comment. In D111409#3124194 <https://reviews.llvm.org/D111409#3124194>, @labath wrote:
> In D111409#3124075 <https://reviews.llvm.org/D111409#3124075>, @teemperor > wrote: > >>> Are you asking for dedicated physical resources for running nightly builds? >> >> I don't think any of the current bots have a Java installation so I think >> it's either that or we get someone with a bot to setup the required Java >> installation. > > I don't have a problem with installing the necessary packages on the bot I > manage, but I cannot subscribe to tracking down any failures (or flaky > tests!) for this configuration (and, in my experience, any new feature like > this is going to have flaky tests). Flaky tests (probably just one) are the > reason that lua integration is not enabled on this bot. Sure, I think it should anyway not be up to any bot owner to track down flaky tests. And that nested_sessions lua test is anyway randomly failing everywhere from what I know. >> FWIW, if no one wants to host a bot for this then I won't mind testing this >> in own CI <https://ci.teemperor.de>, but I am not using buildbot so we'll >> have to see if that is acceptable for the community (I could also migrate it >> to buildbot, but the buildbot interface is just painful to use and I would >> prefer not to). > > I would rather not proliferate test infrastructures. > > I'm not sure which pain points are you referring to, but setting up a > buildbot instance is a lot simpler these days than it used to be (in > particular, you don't need to track down and install any outdated packages). It's not the setup, it's just that the lab.llvm.org interface is far less usable than Jenkins for tracking down regressions in tests (and Jenkins is already not great, so that says something). But that's just my personal preference and I agree that lab.llvm.org should be the central place for infrastructure. Anyway, if @labath can run them on his fancy build bot then I would prefer that over having it on my bot (because I pay out of my own pocket and CPU cycles are $$$). Repository: rLLDB LLDB CHANGES SINCE LAST ACTION https://reviews.llvm.org/D111409/new/ https://reviews.llvm.org/D111409 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
