[petsc-dev] TAP file and testing error

[Scott Kruger]

My summary is that we can just do the easiest fix then and have 
test_tap.log and test_err.log

Scott


On 9/26/19 9:28 AM, Balay, Satish wrote:
> On Thu, 26 Sep 2019, Scott Kruger via petsc-dev wrote:
> 
>>
>>
>> On 9/26/19 12:45 AM, Stefano Zampini wrote:
>>> You usually get the backslash when you trying to be quick and tab-complete
>>> the command :-)
>>
>> Yes, I agree that the makefile should fix this.
>>
>>> and, so far, PETSc accepted this. We should either filter the variable in
>>> the makefile, or change the filenames with their paths.
>>> Scott, are the two PETSC_ARCH specifications really needed in the filename?
>>> I mean first as a folder, than in the filename itself
>>
>> Barry or Satish should confirm, but as I recall the idea is that if you are
>> collecting the the log files into a dashboard, then the PETSC_ARCH labeling
>> scheme is best.
> 
> Well previously - for the dashboard - we did the rename during the copy [from build location to the dashboard].
> 
> If I remember correctly only one generated file had PETSC_ARCH encoded
> - that is PETSC_ARCH/lib/petsc/config/reconfigure-PETSC_ARCH.py - so
> that its easy to copy/save/reuse this script.
> 
> Its not clear to me what type of dashboard we can have in the future -
> and how to get the logs there [beyond the current one at gitlab at
> https://gitlab.com/petsc/petsc/pipelines]
> 
> Satish
> 
>>
>> Pierre Jolivet has an bug report in, and I have the show-test functionality
>> in, so I'll try to get a new MR out soon.
>>
>> Scott
>>
>>
>>>
>>> Il giorno gio 26 set 2019 alle ore 09:38 Matthew Knepley <knepley at gmail.com
>>> <mailto:knepley at gmail.com>> ha scritto:
>>>
>>>      On Wed, Sep 25, 2019 at 8:52 PM Stefano Zampini via petsc-dev
>>>      <petsc-dev at mcs.anl.gov <mailto:petsc-dev at mcs.anl.gov>> wrote:
>>>
>>>          If we specify a PETSC_ARCH with a trailing slash, the current
>>>          testing makefile fails. Can this be fixed?
>>>
>>>
>>>      PETSC_ARCH is a string name and not necessarily a directory. I think
>>>      we should check and fail if it has a slash.
>>>
>>>          Matt
>>>
>>>          *zampins at vulture*:*~/Devel/petsc*$ make -f gmakefile.test test
>>>          globsearch="*densecuda*" PETSC_ARCH=arch-gpu-double-unifmem/
>>>
>>>          touch: cannot touch
>>>          './arch-gpu-double-unifmem//tests/test_arch-gpu-double-unifmem/_tap.log':
>>>          No such file or directory
>>>
>>>          touch: cannot touch
>>>          './arch-gpu-double-unifmem//tests/test_arch-gpu-double-unifmem/_err.log':
>>>          No such file or directory--
>>>          Stefano
>>>
>>>
>>>
>>>      --
>>>      What most experimenters take for granted before they begin their
>>>      experiments is infinitely more interesting than any results to which
>>>      their experiments lead.
>>>      -- Norbert Wiener
>>>
>>>      https://www.cse.buffalo.edu/~knepley/
>>>      <http://www.cse.buffalo.edu/~knepley/>
>>>
>>>
>>>
>>> -- 
>>> Stefano
>>
>>

-- 
Tech-X Corporation               kruger at txcorp.com
5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
Boulder, CO 80303                Fax:   (303) 448-7756