search for: livermore

...he script that has to be changed, using LNTBuilder rather than ClangBuilder. I can see that there are only a few LNTBuilder's in use, and I don't want to break all buildbots, so I'm planning in just changing the gcc12 and gcc20 (with Duncan's permission) to make it stop failing the Livermore loops. Is there some PyDoc / Doxygen documentation on the Zorg classes? I'll be digging it manually in the interim and will send you guys a patch to convert those two buildbots to LNT. Question: Is there any way of changing them locally BEFORE committing the change to Zorg? Or is it changing...

...to be changed, using LNTBuilder rather than ClangBuilder. > > I can see that there are only a few LNTBuilder's in use, and I don't want to > break all buildbots, so I'm planning in just changing the gcc12 and gcc20 (with > Duncan's permission) to make it stop failing the Livermore loops. sorry, what change do you plan to make? Did you work out what the bug is? My basic worry is that it sounds like you are trying to hide the underlying issue rather than fixing it, please correct me if I'm wrong. > > Is there some PyDoc / Doxygen documentation on the Zorg classes...

FYI, attached is a way to reproduce the error without the test-suite paraphernalia. cheers, --renato On 3 January 2013 12:05, Renato Golin <renato.golin at linaro.org> wrote: > David, > > I got some more work on the Livermore Loops and I found out that the issue > is the difference in the parameters between a single step and a multi step > compilation. > > When you compile "clang kernel06.c" it works fine, but when you get all > steps (clang -emit-llvm + llvm-as + opt + llc etc), the defaults op...

On 3 January 2013 21:29, David Blaikie <dblaikie at gmail.com> wrote: > Fair enough - you could write up a patch for the zorg repository to do > this. > Wouldn't requiring every buildbot to use LNT achieve the same thing? --renato -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, Jan 3, 2013 at 1:52 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 3 January 2013 21:29, David Blaikie <dblaikie at gmail.com> wrote: >> >> Fair enough - you could write up a patch for the zorg repository to do >> this. > > > Wouldn't requiring every buildbot to use LNT achieve the same thing? That's how you achieve this goal.

Another issue is that the "fast nightly test" builders aren't working properly: they report success even though they failed (this started happening about one month ago, I don't know what the reason is). While this should be investigated, I'm tempted to just move everything over to LNT instead... Ciao, Duncan.

...'t remember then name of the package or function, and haven't been able to find it after some searching. Does anyone know the name, or have a suggestion to help track it down? Thanks -Don -- -------------------------------------- Don MacQueen Environmental Protection Department Lawrence Livermore National Laboratory Livermore, CA, USA 925-423-1062

...ta. To see this, break your work into two separate steps, like this: tnr.ma <- ma(dat3[1:28], order=3) TNR_moving_average <- forecast(tnr.ma, h=8) I think you will find that the warning comes from the second step. Print tnr.ma and you will see some NAs. -Don -- Don MacQueen Lawrence Livermore National Laboratory 7000 East Ave., L-627 Livermore, CA 94550 925-423-1062 Lab cell 925-724-7509 ? From: Bill Poling <Bill.Poling at zelis.com> Date: Friday, June 1, 2018 at 8:58 AM To: "MacQueen, Don" <macqueen1 at llnl.gov>, array R-help <r-help at r-project.org> Sub...

...at change do you plan to make? Did you work out what the bug is? > My > basic worry is that it sounds like you are trying to hide the underlying > issue > rather than fixing it, please correct me if I'm wrong. Hi Duncan, There are two issues: 1. The LTO bug we found by running Livermore Loops on test-suite. I'm still trying to isolate this and will report as soon as I get a smaller test case. (I sent a tarball earlier to the list on how to reproduce it). Bugs like these will not be caught any more with the standard LNT tests, true, but there's also point 2 below... 2. Bui...

...ke? Did you work out what the bug is? My >> basic worry is that it sounds like you are trying to hide the underlying issue >> rather than fixing it, please correct me if I'm wrong. > > Hi Duncan, > > There are two issues: > > 1. The LTO bug we found by running Livermore Loops on test-suite. I'm still trying to isolate this and will report as soon as I get a smaller test case. (I sent a tarball earlier to the list on how to reproduce it). Bugs like these will not be caught any more with the standard LNT tests, true, but there's also point 2 below...ping &g...

...ing your buildbots, gcc12 is easy to replace by LNT, because the default, AFAICT, is to run only clang tests (check-all I presume), but gcc20 is running the nightly tests, and I'm not sure I should change them to "simple" or keep as "nightly" but do it via LNT. When I added Livermore, I presumed I was running LNT with the nightly variant (nt): ./sandbox/bin/python sandbox/bin/lnt runtest \ --submit ~/devel/llvm/test/perfdb \ nt \ -j8 \ --sandbox sandbox \ --test-suite ~/devel/llvm/test/test-suite \ --cc ~/devel/llvm/build/bin/clang \...

...> is running the nightly tests, and I'm not sure I should change them to > "simple" or keep as "nightly" but do it via LNT. I don't think LNT is able to run the "nightly" version. I believe it only runs the "simple" version. > When I added Livermore, I presumed I was running LNT with the nightly > variant (nt): Strangely enough, I believe LNT's "nt" corresponds to the test-suite's "TEST=simple". I could be wrong, though. > > ./sandbox/bin/python sandbox/bin/lnt runtest \ > --submit ~/devel/llvm/...

On Thu, Jan 3, 2013 at 8:29 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 3 January 2013 16:15, David Blaikie <dblaikie at gmail.com> wrote: >> >> Part of the issue here is whether or not the Make-based execution is >> still maintained/valued. I'm getting the impression that the LNT >> execution may be already, or be becoming, the standard way

All of our internal testers use LNT. LNT behind the scenes just calls the Makefiles appropriately. So it would be impossible to get rid of the makefile execution without gutting LNT as well = p. I will let Daniel comment on the rest of it. On Jan 3, 2013, at 6:55 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 3 January 2013 16:37, David Blaikie <dblaikie at gmail.com>

On Thu, Jan 3, 2013 at 1:04 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 3 January 2013 20:53, Michael Gottesman <mgottesman at apple.com> wrote: >> >> All of our internal testers use LNT. LNT behind the scenes just calls the >> Makefiles appropriately. So it would be impossible to get rid of the >> makefile execution without gutting LNT as well

On 8 January 2013 16:39, David Blaikie <dblaikie at gmail.com> wrote: > I don't think LNT is able to run the "nightly" version. I believe it > only runs the "simple" version. > If my python expertise is correct, LNT is able to run both nightly and simple, but the default is simple. And yes, "nt" is == "simple" in LNT. cheers, --renato

On 3 January 2013 16:37, David Blaikie <dblaikie at gmail.com> wrote: > My only hesitation here is that using LNT as the authoritative runner > does have a little more setup overhead for people wishing to run the > suite (they need to install some extra stuff). > Yes, there is an issue on shared machines, regarding installing new software (mainly the virtualenv, since lnt

On 3 January 2013 20:53, Michael Gottesman <mgottesman at apple.com> wrote: > All of our internal testers use LNT. LNT behind the scenes just calls the > Makefiles appropriately. So it would be impossible to get rid of the > makefile execution without gutting LNT as well = p. > Hi Michael, The idea was never to gut the makefiles or LNT, but to let all buildbots use LNT to call

...uot;rnorm" 20.00 0.02 20.00 0.02 "X11" 20.00 0.02 20.00 0.02 "seq.default" 20.00 0.02 20.00 0.02 "par" -- -------------------------------------- Don MacQueen Environmental Protection Department Lawrence Livermore National Laboratory Livermore, CA, USA -------------------------------------- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe...

...like this: tnr.ma<http://tnr.ma> <- ma(dat3[1:28], order=3) TNR_moving_average <- forecast(tnr.ma<http://tnr.ma>, h=8) I think you will find that the warning comes from the second step. Print tnr.ma<http://tnr.ma> and you will see some NAs. -Don -- Don MacQueen Lawrence Livermore National Laboratory 7000 East Ave., L-627 Livermore, CA 94550 925-423-1062 Lab cell 925-724-7509 From: Bill Poling <Bill.Poling at zelis.com<mailto:Bill.Poling at zelis.com>> Date: Friday, June 1, 2018 at 8:58 AM To: "MacQueen, Don" <macqueen1 at llnl.gov<mailto:macqu...