Re: [gentoo-dev] Gentoo LLVM project needs help!

[Michał Górny]

On Fri, 2022-02-11 at 09:40 -0800, A Schenck wrote:
> On 2/10/22 15:36, Michał Górny wrote:
> > Hi,
> >
> > As you may have noticed, I'm practically maintaining LLVM all by myself.
> > This is a really tedious, time consuming and ungrateful task, and I'm
> > pretty close to burnout.  I'd really appreciate some help.
> >
> > The problem with LLVM that it's a really huge, rapidly moving forward
> > (and breaking things) project.  It needs frequent testing as regressions
> > happen frequently, and we have a good chance of having somebody else fix
> > it if we report them early.  At the same time, testing takes a lot of
> > time.  While ccache is pretty much a must, it doesn't help much long
> > term as the code is changing frequently and invalidating the cache.
> >
> > On top of this, there's almost-overlapping release process and Gentoo
> > slotting that's working so-so at best.  After I've pushed LLVM 13.0.1
> > final, I've had to immediately start testing 14.x and barely managed to
> > get some fixes in before rc1.  Now 14.0.0 is expected soon,
> > simultaneously major changes are happening on the main branch
> > (i.e. 15.x) that also need testing and adjusting the ebuilds to.
> >
> > I barely manage to keep up with amd64 multilib.  Other arches are likely
> > to be broken.  Some specific projects that need help are:
> >
> > 1. Compiler-RT (particularly sanitizers, fuzzer etc.) -- they break
> > quite often on glibc upgrades.  Miraculously, right now 13.0.1
> > and 14.0.0 are clean right now but I'm pretty sure we'll see a new glibc
> > release soon and they're going to require fixing again.
> >
> > 2. OpenMP -- there are many test regressions on every release, and 14.x
> > is particularly bad.  I have no clue about this package, the test output
> > is usually cryptic and I don't really have the time to look into it.
> > Honestly, at this point I would gladly have last rited it if it hadn't
> > had revdeps.
> >
> > 3. LLDB -- while it mostly works and I've managed to fix the worst of
> > it, I still haven't managed to get the test suite fully working.  What's
> > even worse, the test runner just hangs at the very end and I have
> > no clue why or how to debug that.
> You've probly already thought of this but this is when strace comes to
> mind. Is it truly hanging in own code, or waiting on something to change
> in the system that isn't happening?

I don't recall anymore, I haven't had time to try again in a while. 
AFAIR it was the test runner hanging after all tests are done.

-- 
Best regards,
Michał Górny