similar to: [LLVMdev] Kill TestSuiteMakefileGuide.html?

Unfortunately, LNT still uses the Makefiles underneath, and the Makefiles support a few users who use the more advanced hackery they support. We should keep it for the time being. - Daniel On Nov 14, 2012, at 13:30, Sean Silva <silvas at purdue.edu> wrote: > The top of the file says that it is deprecated in favor of LNT. Is > this document still needed? It makes mention of

Sorry for the bother Jim, but I'm calling on you again for guidance about llvm-gcc mentions. What should be done about the mention of llvm-gcc on <http://llvm.org/docs/TestSuiteMakefileGuide.html>? Can we just roughly s/llvm-gcc/clang/ ? Daniel, feel free to provide guidance as well. -- Sean Silva On Wed, Nov 14, 2012 at 4:36 PM, Daniel Dunbar <daniel.dunbar at gmail.com> wrote:

Hi Sean, On 14/11/12 23:53, Sean Silva wrote: > Sorry for the bother Jim, but I'm calling on you again for guidance > about llvm-gcc mentions. What should be done about the mention of > llvm-gcc on <http://llvm.org/docs/TestSuiteMakefileGuide.html>? Can we > just roughly s/llvm-gcc/clang/ ? Daniel, feel free to provide guidance > as well. to some extent llvm-gcc lives on

Hi Sean, The language in "Running the test suite" can be simplified a fair bit, I think. I don't think there's any need to do the multiple stage build, for example. Daniel will probably be better able to provide specifics here. -Jim On Nov 14, 2012, at 2:53 PM, Sean Silva <silvas at purdue.edu> wrote: > Sorry for the bother Jim, but I'm calling on you again for

> And it doesn't match probably because of one of two things (& I forget > which of the two, if either, have been addressed/workaround): > > 1) using cmake instead of configure/make > 2) using git instead of svn > > One or both of these create versions that lnt doesn't understand > (because they don't include the SVN revision number in the clang > version

On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: > I don't know the answer to this question, but I've attached an (old) > version of pybugz that I tweaked a little to work with LLVM bugzilla. You > can probably write such queries on top of this if you feel like figuring > out its API: > Thanks. Looks like most of the pages have some way to

Hi, I'm trying to use LNT to run the test-suite. I followed the instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I get this error: (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox --cc ~/pg/others/llvm/release/bin/clang --test-suite test-suite nt.py:1185: note: inferred C++ compiler under test as:

So, I just tried, and basically it's difficult to make progress due to the print statements (since they induce an immediate syntax error). Since 2.4 doesn't support `from __future__ import print_function`, the only alternative I guess is shimming in a print function. This is a maintenance effort that I don't want to do right now (and, TBQH, I feel that the proper maintainer should be

On Nov 14, 2012, at 10:52 AM, Sean Silva <chisophugis at gmail.com> wrote: > It references release 2.7... is this document worth keeping? > Nuke it from orbit. :) > CC'ing Jim Grosbach since IIRC he recently pulled out some stuff > related to llvm-gcc. > > -- Sean Silva

Hi all, I'm currently in the process of updating the Kaleidoscope tutorials (first and foremost, the ORC/BuildingAJIT ones), and I've noticed a fair few 404s which are lingering within the current visible documentation. Some of these don't seem to have linked to existing pages for a while. I was wondering if there was a way to set up a check in the buildbot to ensure that

nuked in r167961. sorry, Jim, the original mail bounced since I accidentally sent it from another email address that is not subscribed to the list. -- Sean Silva On Wed, Nov 14, 2012 at 2:18 PM, Jim Grosbach <grosbach at apple.com> wrote: > > On Nov 14, 2012, at 10:52 AM, Sean Silva <chisophugis at gmail.com> wrote: > >> It references release 2.7... is this document

Exactly how are you running the tests? Via LNT or directly? If via LNT, make sure you test suite repository is clean (no in tree configure or make results). - Daniel On Oct 28, 2012, at 9:57, Renato Golin <rengolin at systemcall.org> wrote: > Round 2, fight! > > I managed to run many tests (not sure all of them), and some failed, > some didn't. All errors in the

On Wed, Sep 5, 2012 at 7:23 PM, Sean Silva <silvas at purdue.edu> wrote: > Hi, I'm trying to use LNT to run the test-suite. I followed the > instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I > get this error: > > (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox > --cc ~/pg/others/llvm/release/bin/clang --test-suite

On Oct 28, 2012, at 11:19, Renato Golin <rengolin at systemcall.org> wrote: > On 28 October 2012 17:32, Daniel Dunbar <daniel.dunbar at gmail.com> wrote: >> Exactly how are you running the tests? Via LNT or directly? > > Via LNT, like this: > > ./sandbox/bin/python sandbox/bin/lnt runtest nt \ > --sandbox sandbox \ > --test-suite

Hi Sean, If there was a concrete need to move to a newer Python version in order to make lit Python 3 compatible, I would view that as a good reason to move forward. I have little experience writing Python 2 & 3 compatible code, so I'd need to see the patch to make lit Python 3 compatible before I could comment more. - Daniel On Tue, Dec 4, 2012 at 9:15 AM, Sean Silva <silvas at

On 08/11/2013 05:56, Sean Silva wrote: > > > > On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org > <mailto:daniel at zuster.org>> wrote: > > I don't know the answer to this question, but I've attached an > (old) version of pybugz that I tweaked a little to work with LLVM > bugzilla. You can probably write such queries on

On Mon, Jan 7, 2013 at 1:52 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Jan 7, 2013 at 1:46 PM, Daniel Dunbar <daniel at zuster.org> wrote: > > > > > > > > On Mon, Jan 7, 2013 at 1:14 PM, David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> On Mon, Jan 7, 2013 at 12:58 PM, Daniel Dunbar <daniel at

On 28 October 2012 17:32, Daniel Dunbar <daniel.dunbar at gmail.com> wrote: > Exactly how are you running the tests? Via LNT or directly? Via LNT, like this: ./sandbox/bin/python sandbox/bin/lnt runtest nt \ --sandbox sandbox \ --test-suite ~/devel/llvm/test-suite \ --cc ~/devel/llvm/debug/bin/clang++ > If via LNT, make sure you test suite repository is clean (no in

On Mon, Jan 7, 2013 at 1:14 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Jan 7, 2013 at 12:58 PM, Daniel Dunbar <daniel at zuster.org> wrote: > > To weigh in here... > > > > > > On Thu, Jan 3, 2013 at 8:15 AM, David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> +Daniel & Michael who work on the LNT

On Mon, Jan 7, 2013 at 2:17 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Mon, Jan 7, 2013 at 2:05 PM, Daniel Dunbar <daniel at zuster.org> wrote: > > > > > > > > On Mon, Jan 7, 2013 at 1:52 PM, David Blaikie <dblaikie at gmail.com> > wrote: > >> > >> On Mon, Jan 7, 2013 at 1:46 PM, Daniel Dunbar <daniel at