[petsc-dev] nightlybuilds (next vs next-tmp)

[Smith, Barry F.]

> On Nov 15, 2017, at 8:30 PM, Matthew Knepley <knepley at gmail.com> wrote:
> 
> On Wed, Nov 15, 2017 at 8:56 PM, Richard Tran Mills <rtmills at anl.gov> wrote:
> On Sun, Nov 12, 2017 at 9:54 AM, Smith, Barry F. <bsmith at mcs.anl.gov> wrote:
> 
> 
> > On Nov 12, 2017, at 11:21 AM, Matthew Knepley <knepley at gmail.com> wrote:
> >
> > On Sun, Nov 12, 2017 at 12:17 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> > On Sun, 12 Nov 2017, Matthew Knepley wrote:
> >
> > >
> > > Have we tried histogramming test times? It would be nice to know how much
> > > cumulative
> > > time it takes to run 37%, 67%, 95%, etc.
> >
> > I'm not sure what 'histogramming test time' means.
> >
> > The below looked like cumulative times over all tests. I want the time for each test, and then
> > we bin them into say 10s wide bins and see which ones are taking the most time.
> 
>   WE FREAKING NEED TO CONVERT TO THE NEW TEST HARNESS TO DO THIS, then it is easy.
> 
>   So everyone, please, instead of spending twenty minutes a day sending and reading email about testing spend 20 minutes a day converting examples from the old tests to the new harness!!!!!
> 
> For those of us who have no idea how to do this, could someone please give me a pointer or two on where to look for an example or two or some documentation? I should probably be spending a few minutes a day converting some examples, but I don't know how or where to start.
> 
> There is a manual chapter on the test system, but for cut & paste semantics, you can look at SNES which has a lot of converted examples.
> Basically, you take each test entry from the makefile, and move it into the source file itself.

  Richard,

   Scott wrote a tool to semi-automatically do it from the makefile but sadly the tool is currently broken (it had no nightly testing) and like most python code is undebuggable.  Anyways  after you have put a test in the example source code manually as Matt says, you run from PETSC_DIR

    ./config/gmakegentest.py 

this parses all the examples and sets up the scripts that are run to do the testing. Then use, for example, 

  make -f gmakefile test globsearch='*heat*'

to run all tests that have heat in the example name or path. Or you can do


  make -f gmakefile test globsearch='dm*'

to run all tests in the dm directories. Sometimes you need a little trial and error to get the globsearch right to run your example and not others.

You will get a little frustrated the first couple times you do it, just bug us and we'll help you get past the stumbling blocks.

  Barry




   



    
> 
>   Matt
>  
> --Richard
> 
> 
> 
> >
> >    Matt
> >
> > All logs record time. And Karl's script summarizes those times on the
> > dashboard. For eg:
> >
> > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/11/11/maint.html
> >
> > If you want to do some analysis on those times - you can grab the
> > [historical] logs and run the required analysis.
> >
> > Satish
> >
> >
> >
> > --
> > What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> > -- Norbert Wiener
> >
> > https://www.cse.buffalo.edu/~knepley/
> 
> 
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
> 
> https://www.cse.buffalo.edu/~knepley/