search for: c3b9398d101

...all binaries. But maybe that's not how that coverage list is computed? > As for +x permissions on llvm/utils/prepare-code-coverage-artifact.py, > it's an oversight that they are missing. I wasn't able to land a > permissions change via the new monorepo (I get: "Committed c3b9398d101 to > svn", but the commit does not appear). Perhaps you'll have better luck? > I couldn't figure out how to do it via git-svn / `git-llvm push` either, but I added the +x bit in r362561 using an old svn checkout I had lying around. > > best, > vedant > > On May...

Probably this job: lab.llvm.org:8080/green/job/clang-stage2-coverage-R/ 💬 from 📱 > On May 31, 2019, at 3:35 PM, Duncan Exon Smith <dexonsmith at apple.com> wrote: > > +Chris Matthews, do you know where the configs are stored for this? > >> On 2019 May 31, at 12:39, Chris Bieneman <beanz at apple.com> wrote: >> >> Hey Nico, >> >> I'm

...group under the 'all' and 'llvm' entries. > > > As for +x permissions on llvm/utils/prepare-code-coverage-artifact.py, >> it's an oversight that they are missing. I wasn't able to land a >> permissions change via the new monorepo (I get: "Committed c3b9398d101 to >> svn", but the commit does not appear). Perhaps you'll have better luck? >> > > I couldn't figure out how to do it via git-svn / `git-llvm push` either, > but I added the +x bit in r362561 using an old svn checkout I had lying > around. > > > Thank...

...9;all' and 'llvm' entries. >> >> >> As for +x permissions on llvm/utils/prepare-code-coverage-artifact.py, >>> it's an oversight that they are missing. I wasn't able to land a >>> permissions change via the new monorepo (I get: "Committed c3b9398d101 to >>> svn", but the commit does not appear). Perhaps you'll have better luck? >>> >> >> I couldn't figure out how to do it via git-svn / `git-llvm push` either, >> but I added the +x bit in r362561 using an old svn checkout I had lying >> arou...