Will do, thanks!
On Tue, Mar 28, 2023 at 7:28 PM Jed Brown wrote:
> Great that you got it working. We would accept a merge request that made
> our infrastructure less PETSc-specific so long as it doesn't push more
> complexity on the end user. That would likely make it easier for you to
> pull
Great that you got it working. We would accept a merge request that made our
infrastructure less PETSc-specific so long as it doesn't push more complexity
on the end user. That would likely make it easier for you to pull updates in
the future.
Daniele Prada writes:
> Dear Matthew, dear
Dear Matthew, dear Jacob,
Thank you very much for your useful remarks. I managed to use the PETSc
Testing System by doing as follows:
1. Redefined TESTDIR when running make
2. Used a project tree similar to that of PETSc. For examples, tests for
'package1' are in $MYLIB/src/package1/tests/
3. cp
On Mon, Mar 27, 2023 at 10:19 AM Jacob Faibussowitsch
wrote:
> Our testing framework was pretty much tailor-made for the PETSc src tree
> and as such has many hard-coded paths and decisions. I’m going to go out on
> a limb and say you probably won’t get this to work...
>
I think we can help you
Our testing framework was pretty much tailor-made for the PETSc src tree and as
such has many hard-coded paths and decisions. I’m going to go out on a limb and
say you probably won’t get this to work...
That being said, one of the “base” paths that the testing harness uses to
initially find
Hello everyone,
I would like to use the PETSc Testing System for testing a package that I
am developing.
I have read the PETSc developer documentation and have written some tests
using the PETSc Test Description Language. I am going through the files in
${PETSC_DIR}/config but I am not able to
