> 24. 1. 2018 v 22:55, Scott Kruger :
>
>
>
> On 1/24/18 6:50 AM, Vaclav Hapla wrote:
>>> 24. 1. 2018 v 14:45, Vaclav Hapla :
>>>
>>> How should I specify output files for {{...}} with different outputs,
>>> please?
>> Oh I see, {{...}separateoutput} is meant literally. But in that case
>>
src/docs/tex/manual/developers.tex there is also a make file that generates
the PDF.
Barry
The document should provide information about the location of its source.
> On Jan 25, 2018, at 2:19 AM, Vaclav Hapla wrote:
>
>
>
>> 24. 1. 2018 v 22:55, Scott Kruger :
>>
>>
>>
>> On 1/24
Are you going to keep the old makefiles? (I mean
${PETSC_DIR}/lib/petsc/conf/test) In SLEPc we still use makefiles for the
tests. I should move to the new system, but don't have time at the moment.
Jose
> El 25 ene 2018, a las 5:47, Smith, Barry F. escribió:
>
>
> PETSc developers,
>
>
Awesome!
As a contributor, what I am I supposed to do when a test fails due to some
error of mine?
What's the procedure to be able to run a test "under my own control" (be
able to see what's actually being executed, and what's failing in the diff)
so that I can fix my error?
That is, I want to be
On 1/25/18 4:35 AM, Patrick Sanan wrote:
This following is what I would try, given my limited knowledge of how
things work and after a quick scan of the docs. Is this as intended or
is there an easier way?
You pretty much have it.
--
I mak
> On Jan 25, 2018, at 2:42 AM, Jose E. Roman wrote:
>
> Are you going to keep the old makefiles? (I mean
> ${PETSC_DIR}/lib/petsc/conf/test) In SLEPc we still use makefiles for the
> tests.
Yes
I have stripped out some stuff like the TESTEXAMPLES_n definitions but we
can put back anyt
Patrick
This is very good feed back and understanding. Since you are discovering
all this partially documented material you can add the work flows as discussed
below to the developers guide (and put your name on the guide) so the future
developers don't need to guess and extrapolate as y
