On Wed, 21 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > If you want to point users to our trunk we need to see your test > results. Period.
This is a good point. I'd feel much much happier about my "libmesh/testing gets synched to trunk when it passes tests" plan if those tests included all the various rigorous application tests we have rather than just the relatively rigor-free internal logic tests that get hit by our examples. Presuming that most of those applications aren't going to be available for public release in the immediate future, we'd need to have some way for the central buildbot (or trac, whatever) server to see external results, and moreover to get *synchronized* results rather than results testing whatever revision happens to be the latest available when the tests are run. Even if GRINS-buildbot reports success with r7001 and FINS-buildbot reports success with r7002 and MOOSE-trac reports success with r7004, that doesn't mean that any of those releases are guaranteed free of failures with all three test suites. > quit bitching This wasn't called for. --- Roy ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
