similar to: Coverage Update on http://llvm.org/reports/coverage/

> On May 19, 2016, at 8:59 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > This is now fixed: http://llvm.org/reports/coverage/ > I skimmed the results, and it seems that there

> On May 16, 2016, at 11:58 AM, Sylvestre Ledru <sylvestre at debian.org> wrote: > > Le 16/05/2016 à 19:19, Mehdi Amini a écrit : >> Hi, >> >> Anyone knows who is involved with this page on llvm.org? Which bot is updating it? (it seems stalled right now) > I am in charge of this. I had some recent issues with cmake but I think > I fixed them today. >

Hi Sylvestre, it seems the code coverage runs are not updated since a couple of months. http://llvm.org/reports/coverage/tools/polly/lib/Support/SCEVValidator.cpp.gcov.html The last run was on 2017-05-20 02:07:48. Are you still maintaining these? Is this on purpose? Any chance this could be fixed? Best, Tobias

Hi Sylvestre, On Sat, 12 Mar 2016, Sylvestre Ledru wrote: > I am working on it as we speak. Hopefully, most of the 3.8 & 3.9 > packages are going to be green by next week. Any updates on that? It appears that Precise repositories are now in order, but all the others (and, most importantly, Trusty) are still not updated. Also, 3.9 packages are not mentioned on the web page,

> On Sep 21, 2016, at 12:56 PM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Sep 21, 2016 at 12:32 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> On Sep 21, 2016, at 9:36 AM, Kostya Serebryany via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:

Thanks, I fixed the typo with Xenial. I don't know if I want to bring back llvm-jenkins.d.n again yet. if people see an interest in it, why not :) Le 27/04/2016 à 13:06, Alexander Kornienko a écrit : > ... and http://llvm-jenkins.debian.net/ seems to be down. Sorry for > bugging you with all of this, and thanks for fixing the > clang-modernize thingy so quickly! > > On Wed,

After some thinking on this idea, it would not work because I need / want to use Debian/Ubuntu package to do the build and clang 3.4 is not built on these architecture :( So, if I bootstrap clang 3.4, I will have a dependency on libstdc++ 4.8... :/ On 25/12/2013 22:23, Arnaud Allard de Grandmaison wrote: > Hi Sylvestre, > > The easiest is probably to have a dependency to (and use)

Le 06/05/2015 21:05, Renato Golin a écrit : > On 6 May 2015 at 19:15, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: >> I could not easily locate this on http://llvm.org/reports/coverage/ so >> asking here: what workload is the coverage computed over? IOW, what >> all does the bot run to get this coverage information? > Nothing is clear in that page. No

Hello, Just a quick refresh, on llvm.org/apt/ [1], I am rebuilding the sources of LLVM to create snapshot packages for the stable branches and development branches (currently, 3.4, in the hope of point releases and 3.5). This currently targets 2 releases of Debian and 4 of Ubuntu [2] and the llvm toolchain is built using the compiler shipped with the distribution. Following the recent

> On Sep 21, 2016, at 9:36 AM, Kostya Serebryany via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Exciting! > > (btw, I'd prefer libfuzzer at googlegroups.com <mailto:libfuzzer at googlegroups.com> for such discussions, please start new topics there) You mean a LLVM library has a separate mailing-list? Why? — Mehdi > > I can reproduce this too, but

On Mon, May 9, 2016 at 4:46 PM Sylvestre Ledru <sylvestre at debian.org> wrote: > Le 09/05/2016 à 07:34, Paweł Bylica a écrit : > > llvm-3.8-dev is broken: > > > > CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): > > include could not find load file: > > > > /usr/share/llvm/cmake/LLVMExports.cmake > Brad King helped me

Hello all, For CI testing of LDC with LLVM trunk we use CircleCI, which offers Ubuntu Trusty 14.04. We use apt.llvm.org, but the latest update of the "nightly" package is now more than a month ago. Previously the update rate was once a week, which was OK as it meant that we only had a few days of test breakage after an API change (and after a dev updated LDC to build with a locally

Hello, Le 29/08/2019 à 01:02, Artem Dergachev a écrit : > Yay thx! > > Sylvestre, is there anything i can help you with in order to get the reports page back up? Sorry, it took me a while to get that back but here is the report of r371718: https://llvm.org/reports/scan-build/ > I'd also indeed love to spam people with warnings that they introduced, even if in the form of a

> On Sep 21, 2016, at 1:25 PM, Kostya Serebryany <kcc at google.com> wrote: > > > > On Wed, Sep 21, 2016 at 12:58 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> On Sep 21, 2016, at 12:56 PM, Kostya Serebryany <kcc at google.com <mailto:kcc at google.com>> wrote: >> >> >>

On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > This is still maintained. However the cmake transition (for both 3.8 and > 3.9) wasn't simple... While it should be fine for debian, it might need > more work for old Ubuntu (back port of cmake) Hi Sylvestre, Thank you for the clarification! Any ETAs on when the APT repositories are going to be updated with LLVM 3.8 & 3.9 builds?

On Wed, Mar 9, 2016 at 10:30 PM, Sylvestre Ledru via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Le 09/03/2016 à 21:44, Yury V. Zaytsev a écrit : > > On Wed, 9 Mar 2016, Sylvestre Ledru wrote: > > > >> This is still maintained. However the cmake transition (for both 3.8 > >> and 3.9) wasn't simple... While it should be fine for debian, it >

On Wed, 13 Apr 2016 at 08:10 Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I'd like to shime in here. These apt repository used to contain packages > named llvm-3.8-tools containing, amongst other things, the lit python > library used to test llvm. It seems that it went away recently and I have > travis build failing because of this. > > What is

Le 09/05/2016 à 16:59, Paweł Bylica a écrit : > On Mon, May 9, 2016 at 4:46 PM Sylvestre Ledru <sylvestre at debian.org > <mailto:sylvestre at debian.org>> wrote: > > Le 09/05/2016 à 07:34, Paweł Bylica a écrit : > > llvm-3.8-dev is broken: > > > > CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 > (include): >

On 18/02/2015 23:29, Alexey Samsonov wrote: > > On Tue, Feb 17, 2015 at 6:23 PM, Anna Zaks <ganna at apple.com <mailto:ganna at apple.com>> wrote: > > >> On Feb 17, 2015, at 4:00 PM, Alexey Samsonov <vonosmas at gmail.com <mailto:vonosmas at gmail.com>> wrote: >> >> >> On Tue, Feb 17, 2015 at 3:37 PM, Anna Zaks <ganna at

llvm-3.8-dev is broken: CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): include could not find load file: /usr/share/llvm/cmake/LLVMExports.cmake llvm-3.7-dev is ok. Why is it so error prone for so many years? On Sun, May 8, 2016 at 11:31 PM Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > So, it turns out that the secret sauce to