This issue is not in petsc-3.3 but looks like it was introduced at:

http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7

I switched nightly builds back from petsc33 to petsc-dev on june 27-ish..

satish

On Thu, 5 Jul 2012, Barry Smith wrote:

> 
> On Jul 5, 2012, at 4:19 AM, Jed Brown wrote:
> 
> > This is years old, but in any case, fixed now: 
> > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e
> 
>    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?
> 
> 
> > 
> > On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> > 
> > /bin/sh: -c: line 0: syntax error near unexpected token `done'
> > /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'
> > make[7]: [runex37] Error 2 (ignored)
> > /bin/sh: -c: line 0: syntax error near unexpected token `done'
> > /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'
> > make[7]: [runex37_1] Error 2 (ignored)
> > /bin/sh: -c: line 0: syntax error near unexpected token `done'
> > /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'
> > make[7]: [runex37_2] Error 2 (ignored)
> > 
> > At least test your rule before pushing
> > 
> > 
> > 
> > 
> 
> 

Reply via email to