On Thu, Jul 5, 2012 at 10:37 AM, 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 5, 2012 at 5:35 AM, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
On Jul 5, 2012, at 4:19 AM, Jed Brown wrote:<br>
<br>
> This is years old, but in any case, fixed now: <a href="http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e" target="_blank">http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e</a><br>
<br>
</div> How can it possibly be years old? You're saying that this message has appeared every night during the nightly tests and every time someone did make alltests and during every test Satish made before the release?<br>
</blockquote><div><br></div></div><div>Oops, I read "hg annotate" incorrectly. It was in</div><div><br></div><div><a href="http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7" target="_blank">http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7</a></div>
<div><br></div><div>which was merged in</div><div><br></div><div><a href="http://petsc.cs.iit.edu/petsc/petsc-dev/rev/9dfe4a92ca2c" target="_blank">http://petsc.cs.iit.edu/petsc/petsc-dev/rev/9dfe4a92ca2c</a></div><div><br>
</div><div>I don't understand the motivation for unrolling the shell loop, but then referencing a file that doesn't match the target name.</div></div></blockquote><div><br></div><div>I unrolled the shell loop so that the shell code can be processed by Python, and eventually converted to Python tests.</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><div><br>
<br>
><br>
> On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
> /bin/sh: -c: line 0: syntax error near unexpected token `done'<br>
> /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp'<br>
> make[7]: [runex37] Error 2 (ignored)<br>
> /bin/sh: -c: line 0: syntax error near unexpected token `done'<br>
> /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp'<br>
> make[7]: [runex37_1] Error 2 (ignored)<br>
> /bin/sh: -c: line 0: syntax error near unexpected token `done'<br>
> /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out ex37_2.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_2, diffs above \n========================================="; done; /bin/rm -f -f ex37_2.tmp'<br>
> make[7]: [runex37_2] Error 2 (ignored)<br>
><br>
> At least test your rule before pushing<br>
><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div></div><br>
</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>