Great. Thanks!
Satish
On Fri, 7 Sep 2018, Jose E. Roman wrote:
> It is in master now, so the error should be fixed.
> Jose
>
>
> > El 7 sept 2018, a las 3:02, Satish Balay escribió:
> >
> > I see the relvent slepc changes are in alex/test-harness
> >
> > I've merged
It is in master now, so the error should be fixed.
Jose
> El 7 sept 2018, a las 3:02, Satish Balay escribió:
>
> I see the relvent slepc changes are in alex/test-harness
>
> I've merged balay/remove-Regression.py branch into petsc master. So current
> slepc master [with petsc master] gives:
I see the relvent slepc changes are in alex/test-harness
I've merged balay/remove-Regression.py branch into petsc master. So current
slepc master [with petsc master] gives:
Checking environment... done
Checking PETSc installation... done
Checking ARPACK... done
Checking LAPACK library...
It works for us. Thanks.
Jose
> El 5 sept 2018, a las 15:15, Satish Balay escribió:
>
> I pushed the change to balay/remove-Regression.py
>
> Satish
>
> On Mon, 3 Sep 2018, Jose E. Roman wrote:
>
>> We are almost done with migrating SLEPc tests to the new test harness. If
>> you want, you
I pushed the change to balay/remove-Regression.py
Satish
On Mon, 3 Sep 2018, Jose E. Roman wrote:
> We are almost done with migrating SLEPc tests to the new test harness. If you
> want, you can remove Regression.py from PETSc, as well as any makefile rules
> that might remain for legacy
Or is the issue with the name "lib/petsc/conf/test"?
I guess it could be renamed lib/petsc/conf/rules_examples [or something else]
Satish
On Sat, 7 Jul 2018, Satish Balay wrote:
> Sorry - I don't quiet understand what you are suggesting here.
>
> On Thu, 5 Jul 2018, Jed Brown wrote:
>
> >
Sorry - I don't quiet understand what you are suggesting here.
On Thu, 5 Jul 2018, Jed Brown wrote:
> "Smith, Barry F." writes:
>
> >> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote:
> >>
> >> When can we delete the legacy test system? Are we currently using it
> >> anywhere?
> >
> > Make
I'm fine with stripping out as much of the old test stuff as reasonably
possible.
Barry
> On Jul 5, 2018, at 8:36 PM, Jed Brown wrote:
>
> "Smith, Barry F." writes:
>
>>> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote:
>>>
>>> When can we delete the legacy test system? Are we
"Smith, Barry F." writes:
>> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote:
>>
>> When can we delete the legacy test system? Are we currently using it
>> anywhere?
>
> Make test currently requires the test include file
Surely this indirection and logging isn't needed in all the
I think SLEPc primarily relies on regression.py in configure.
${PETSC_DIR}/lib/petsc/conf/test has targets to support:
cd src/ksp/ksp/examples/tutorials
make ex2
and ${PETSC_DIR}/lib/petsc/conf/test.common has targets to support:
make alltests [used by nightlybuilds]
Satish
On Fri, 6 Jul
Well, if you want to remove it, I can just insert
${PETSC_DIR}/lib/petsc/conf/test in SLEPc's repository, so not a big problem.
> El 6 jul 2018, a las 7:46, Jose E. Roman escribió:
>
> SLEPc still uses the legacy test system. I have not had time to move to the
> new test harness.
> Jose
>
>
SLEPc still uses the legacy test system. I have not had time to move to the new
test harness.
Jose
> El 6 jul 2018, a las 2:42, Smith, Barry F. escribió:
>
>
>
>> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote:
>>
>> When can we delete the legacy test system? Are we currently using it
>>
> On Jul 5, 2018, at 5:36 PM, Jed Brown wrote:
>
> When can we delete the legacy test system? Are we currently using it
> anywhere?
Make test currently requires the test include file
Barry
On Thu, Jul 5, 2018 at 6:07 PM Satish Balay wrote:
> Ok - there is some confusion here.
>
> The test harness does not use targets in
> examples/[tests,tutorials]/makefile.
>
> However we want to keep the functionality of us/users compiling
> individual examples manually - without going through
Ok - there is some confusion here.
The test harness does not use targets in
examples/[tests,tutorials]/makefile.
However we want to keep the functionality of us/users compiling
individual examples manually - without going through the test harness.
i.e the following should continue to work:
cd
Satish Balay writes:
> On Thu, 5 Jul 2018, Jed Brown wrote:
>
>> When can we delete the legacy test system? Are we currently using it
>> anywhere?
>
> [Don't know exactly which parts we would delete] - but the new targets
> cover ex*[f,f90] type examples - and not anything else.
Which targets
On Thu, 5 Jul 2018, Jed Brown wrote:
> When can we delete the legacy test system? Are we currently using it
> anywhere?
[Don't know exactly which parts we would delete] - but the new targets
cover ex*[f,f90] type examples - and not anything else.
So all other examples that don't fit this
On Thu, Jul 5, 2018 at 5:37 PM Jed Brown wrote:
> When can we delete the legacy test system? Are we currently using it
> anywhere?
>
Not I said the fox.
Matt
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to
18 matches
Mail list logo
