Re: [petsc-dev] Valgrind problems

2019-12-08 Thread Scott Kruger
Once MR!2329 is merged in, all of these test harness annoyances should be fixed. It wasn't a single issue, but rather a bunch of stdout/stderr and error code issues that were fixed in multiple MR's. Scott On 12/8/19 12:11 AM, Smith, Barry F. wrote: On Dec 7, 2019, at 6:00 PM, Matthe

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Smith, Barry F.
> On Dec 7, 2019, at 6:00 PM, Matthew Knepley wrote: > > Nope, you are right. > > Thanks, > > Matt > > On Sat, Dec 7, 2019 at 6:19 PM Balay, Satish wrote: > The fix for this is in 363424266cb675e6465b4c7dcb06a6ff8acf57d2 > > Do you have this commit in your branch - and still seeing

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Matthew Knepley
Nope, you are right. Thanks, Matt On Sat, Dec 7, 2019 at 6:19 PM Balay, Satish wrote: > The fix for this is in 363424266cb675e6465b4c7dcb06a6ff8acf57d2 > > Do you have this commit in your branch - and still seeing issues? > > Satish > > On Sat, 7 Dec 2019, Patrick Sanan wrote: > > > I wa

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Balay, Satish
The fix for this is in 363424266cb675e6465b4c7dcb06a6ff8acf57d2 Do you have this commit in your branch - and still seeing issues? Satish On Sat, 7 Dec 2019, Patrick Sanan wrote: > I was actually wondering about this, as in some cases valgrind errors appear > and sometimes they don't, but I did

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Balay, Satish
You need to rebase your branches over latest master before submitting the test pipeline. Satish On Sat, 7 Dec 2019, Matthew Knepley wrote: > On Sat, Dec 7, 2019 at 4:00 PM Smith, Barry F. wrote: > > > > >Can you point to the pipeline test output where it fails for issue that > > mentions

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Matthew Knepley
On Sat, Dec 7, 2019 at 4:04 PM Patrick Sanan wrote: > I was actually wondering about this, as in some cases valgrind errors > appear and sometimes they don't, but I didn't dig into it too deeply. > > Here's my workaround, FWIW, which shows some output for that test on > master. > > I don't see an

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Matthew Knepley
On Sat, Dec 7, 2019 at 4:00 PM Smith, Barry F. wrote: > >Can you point to the pipeline test output where it fails for issue that > mentions it? Satish had issues posted for each valgrind problem (I still > have the biharmonic I will try to fix today) and I can't find that one. > I wonder if

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Patrick Sanan
I was actually wondering about this, as in some cases valgrind errors appear and sometimes they don't, but I didn't dig into it too deeply. Here's my workaround, FWIW, which shows some output for that test on master. I don't see any output when I just run the tests like this: VALGRIND=1 mak

Re: [petsc-dev] Valgrind problems

2019-12-07 Thread Smith, Barry F.
Can you point to the pipeline test output where it fails for issue that mentions it? Satish had issues posted for each valgrind problem (I still have the biharmonic I will try to fix today) and I can't find that one. Thanks > On Dec 7, 2019, at 2:45 PM, Matthew Knepley wrote: > > I a

[petsc-dev] Valgrind problems

2019-12-07 Thread Matthew Knepley
I am trying to clean up valgrind errors. However this one dm_impls_plex_tests-ex1_fluent_2 is valgrind clean on my machine. Does anyone get it to output something? Thanks, Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interest