[Users] Piraha in the Flesh
jtao at cct.lsu.edu
Fri Feb 22 10:36:07 CST 2013
The call back functions just provide a way to customize the handling
of warn and info output. Since all the registered handlers are iterated,
a new handler doesn't replace the old handler.
Some changes are necessary to change the default behaviour for failed
test runs. As for comparing the output files, it is currently done with
a perl script basically doing a diff. I would again suggest that we
move to HDF5. Also some performance test would be also good in line
with success/fail test.
Recently I started looking into a project called Codespeed.
A sample usage can be found at
We might want learn something from it.
On 02/22/2013 10:10 AM, Ian Hinder wrote:
> On 22 Feb 2013, at 16:57, Jian Tao <jtao at cct.lsu.edu> wrote:
>> Hi Frank,
>> I worked on warn_callback and info_callback back in 2005. It seems
>> they have been added to the trunk.
>> I sent around a sample implementation that dump all info and warn
>> to files. Since the function iterates through all registered
>> callbacks, there could be multiple ways warn and info could be
>> I will try to find a sample implementation and send to the list.
> The test mechanism will currently report the test as failed if Cactus
> returns a nonzero exit code. We would need to add a parameter
> (probably to the flesh) to tell it to return a zero exit code, and to
> write the error message to a file. We would then need the test
> mechanism to be able to reliably diff the error message text. At the
> moment, I think the test mechanism assumes that output files are
> columns of numbers; is that correct?
>> Regards, Jian On 02/22/2013 09:09 AM, Frank Loeffler wrote:
>>> Is there a way to tell Cactus to save error messages to a file?
>>> If so, we should use this to create testsuites testing error
>> _______________________________________________ Users mailing list
>> Users at einsteintoolkit.org
More information about the Users