On Thu, Jul 26, 2012 at 2:31 PM, Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">jedbrown@mcs.anl.gov</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div class="im">On Thu, Jul 26, 2012 at 2:17 PM, Matthew Knepley <span dir="ltr"><<a href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>></span> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div class="gmail_quote"><div>You can tell from the primary key what it is. If the primary key is wrong, it does not help you in your scenario as it could be</div><div>misspelled, or intended to be put in another directory. This is dubious at best.</div>
</div></blockquote><div><br></div></div><div>I don't need the primary key to be "right" to have good diagnostics, I just need to know that the Test() declaration (which executes code at the time the test is created) is inconsistent. My error message tells you the line that is bad. This is important.</div>
<div class="im">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div></div></div></blockquote></div></div></blockquote></div><div>
We should have a discussion about whether we want to support this after 3.3.</div><div><div> </div></div></div></blockquote><div><br></div></div><div>What's the problem? Is builder.py having trouble figuring out how to link PETSc in general? Maybe it should use "make getlinklibs". ;-D</div>
<div><br></div><div>Note that people occasionally ask for minimal builds for low-level functionality. Barry was even asking if it would be feasible to have a way to build only some KSPs, PCs, and matrix formats. I like that the option keeps us honest.</div>
<div class="im">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><div> </div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><div></div></div></div></blockquote></div></div></blockquote></div><div>No no. Your original make log is in PETSC_ARCH/conf/make.log. It should never be corrupted. You</div><div>remove the link at make.log.bkp.</div>
</div></blockquote><div><br></div></div><div>Well, that's an interesting (and confusing) idea for how it <b>could</b> work some day, but it's not how it currently works.</div></div></blockquote><div><br></div><div>
How the fuck is that confusing? Is this just for the sake of argument. This is how we DESIGNED configure to work</div><div>and treat logs. Were you absent that day? Do you have a note?</div><div><br></div><div> Matt</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><div><div> </div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>
<div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"></div></blockquote></div>
</div></blockquote><div><br></div></div></div><div>Same way we do in the makefiles now. It has an attribute "complex", "superlu", etc.</div></div></blockquote><div><br></div></div><div>So what you're saying is that your system could be extended to do this? I'm not disagreeing, but I think my suggestion is more maintainable and extensible. As I said in my first reply, the differences are mostly cosmetic, but I think there is good reason to prefer the form I suggest. The important thing in either case is to have a database of tests so we can program behavior.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div></div></div></blockquote></div></div></blockquote></div></div>
Some have these.</blockquote><div><br></div><div>Held separately?</div><div><br></div><div><div>regressionRequirements = {'src/vec/vec/examples/tests/ex31': set(['Matlab'])</div><div> }</div>
</div><div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>