[petsc-dev] Nightly tests quick summary page

2013-01-24 Thread Karl Rupp
Hi Jed, > It's also a matter of the need for a 'yes/no'-testing. Running a > fixed test like > if (err > eps) fail_test(); > is probably too harsh and we instead use some kind of continuous > metric to judge the outcome of the test. > > > Agreed, but note that an arbitrarily

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Jed Brown
On Wed, Jan 23, 2013 at 10:13 PM, Karl Rupp wrote: > It's also a matter of the need for a 'yes/no'-testing. Running a fixed > test like > if (err > eps) fail_test(); > is probably too harsh and we instead use some kind of continuous metric to > judge the outcome of the test. > Agreed, but note

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Jed Brown
On Wed, Jan 23, 2013 at 10:03 PM, Matthew Knepley wrote: > I am torn here. I would bet serious money that I can write a parser for > our current numerical output in 1/10 > of the time it takes to write new output/parsers and setup all the > associated infrastructure (databases). If > all we ever

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Karl Rupp
Hi, > MOOSE puts all their test output into exodus files and uses exodiff. > That has the advantage of being structured enough that it can be diffed > with rtol and atol. > > OTOH, we have a challenge that's mostly distinct from a discretization > package. We're not testing error in a discretizati

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Matthew Knepley
On Wed, Jan 23, 2013 at 9:29 PM, Jed Brown wrote: > > On Wed, Jan 23, 2013 at 9:08 PM, Matthew Knepley wrote: > >> I am always skeptical of big programs to overall a large piece of >> infrastructure that works fairly well. >> >> However, there is a really simple thing that we need which would mak

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Karl Rupp
Hi, > Any thoughts/experiences? I know Jed has good plans on a testing > environment, so this is not meant to be an assault on him ;-) > > > I am always skeptical of big programs to overall a large piece of > infrastructure that works fairly well. Yes, the overall complexity should be eas

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Jed Brown
On Wed, Jan 23, 2013 at 9:08 PM, Matthew Knepley wrote: > I am always skeptical of big programs to overall a large piece of > infrastructure that works fairly well. > > However, there is a really simple thing that we need which would make us > much much much better > at using our own tests. We ne

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Matthew Knepley
On Wed, Jan 23, 2013 at 4:37 PM, Karl Rupp wrote: > Dear PETScians, > > I've adopted the HTML summary page script for the style checks a little in > order to have a quick overview of the results of our nightly tests: > > http://krupp.iue.tuwien.ac.at/**petsc-test/

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Karl Rupp
Hi Jed, > Dear PETScians, > > I've adopted the HTML summary page script for the style checks a > little in order to have a quick overview of the results of our > nightly tests: > http://krupp.iue.tuwien.ac.at/__petsc-test/ > >

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Jed Brown
On Wed, Jan 23, 2013 at 4:37 PM, Karl Rupp wrote: > Dear PETScians, > > I've adopted the HTML summary page script for the style checks a little in > order to have a quick overview of the results of our nightly tests: > > http://krupp.iue.tuwien.ac.at/**petsc-test/

[petsc-dev] Nightly tests quick summary page

2013-01-23 Thread Karl Rupp
Dear PETScians, I've adopted the HTML summary page script for the style checks a little in order to have a quick overview of the results of our nightly tests: http://krupp.iue.tuwien.ac.at/petsc-test/ It doesn't do anything fancy, particularly no automatic bisection or the like, but it gives