Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

The tests are run in parallel - but most other tests are sequential.

When I tried to reproduce I ran sequentially [as in 'make -f gmakefile' without 
-j] - and some of them hung..

Satish

On Fri, 6 Apr 2018, Karl Rupp wrote:

> Hi again,
> 
> the reason for the higher number of timeouts is likely to be due to the higher
> number of GPU tests. GPU builds that formerly only used CUSP now run against
> the CUDA backend, which has a higher number of tests. Also, the CUDA backend
> uses CUBLAS and CUSPARSE, whereas CUSP used its own kernels. As far as I know,
> CUBLAS and CUSPARSE initialization is fairly slow on the M2090.
> 
> Best regards,
> Karli
> 
> 
> On 04/06/2018 09:13 PM, Karl Rupp wrote:
> > Hi,
> > 
> >> The CUDA tests are hanging/timing-out more often now. For eg:
> >> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/06/examples_next_arch-cuda-double_es.log
> >>  
> >>
> >>
> >> And I did see some build where they didn't get killed due to timeout. For
> >> eg:
> >> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/examples_next_arch-cuda-double_es.log
> >>  
> >>
> >>
> >> This is on M2090.  I can see them getting stuck on es.mcs [when I run
> >> manually - and check with nvidia-smi]
> >>
> >> When i run these tests manually on GTX1050 (frog.mcs) - they zip through..
> >> Any idea why they get stuck on M2090? [more frequently than random hangs..]
> > 
> > no, I don't know why this is the case. All my local tests finish quickly,
> > too. I noticed last summer that there is higher startup overhead on the
> > M2090 than on more recent GPUs, but that was in the seconds regime, not in
> > minutes.
> > 
> > Are the tests run in parallel? If so, then maybe the parallel initialization
> > of GPUs is slowing things down.
> > 
> > Best regards,
> > Karli
> 

Re: [petsc-dev] upcoming release and testing [v2]

[Karl Rupp]

Hi again,

the reason for the higher number of timeouts is likely to be due to the 
higher number of GPU tests. GPU builds that formerly only used CUSP now 
run against the CUDA backend, which has a higher number of tests. Also, 
the CUDA backend uses CUBLAS and CUSPARSE, whereas CUSP used its own 
kernels. As far as I know, CUBLAS and CUSPARSE initialization is fairly 
slow on the M2090.


Best regards,
Karli


On 04/06/2018 09:13 PM, Karl Rupp wrote:

Hi,


The CUDA tests are hanging/timing-out more often now. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/06/examples_next_arch-cuda-double_es.log 



And I did see some build where they didn't get killed due to timeout. 
For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/examples_next_arch-cuda-double_es.log 



This is on M2090.  I can see them getting stuck on es.mcs [when I run 
manually - and check with nvidia-smi]


When i run these tests manually on GTX1050 (frog.mcs) - they zip 
through..
Any idea why they get stuck on M2090? [more frequently than random 
hangs..]


no, I don't know why this is the case. All my local tests finish 
quickly, too. I noticed last summer that there is higher startup 
overhead on the M2090 than on more recent GPUs, but that was in the 
seconds regime, not in minutes.


Are the tests run in parallel? If so, then maybe the parallel 
initialization of GPUs is slowing things down.


Best regards,
Karli

Re: [petsc-dev] upcoming release and testing [v2]

[Karl Rupp]

Hi,


The CUDA tests are hanging/timing-out more often now. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/06/examples_next_arch-cuda-double_es.log

And I did see some build where they didn't get killed due to timeout. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/examples_next_arch-cuda-double_es.log

This is on M2090.  I can see them getting stuck on es.mcs [when I run manually 
- and check with nvidia-smi]

When i run these tests manually on GTX1050 (frog.mcs) - they zip through..
Any idea why they get stuck on M2090? [more frequently than random hangs..]


no, I don't know why this is the case. All my local tests finish 
quickly, too. I noticed last summer that there is higher startup 
overhead on the M2090 than on more recent GPUs, but that was in the 
seconds regime, not in minutes.


Are the tests run in parallel? If so, then maybe the parallel 
initialization of GPUs is slowing things down.


Best regards,
Karli

Re: [petsc-dev] upcoming release and testing [v2]

[Richard Tran Mills]

Satish: Oops, I noticed that the order of the developer photos got messed
up (Hong and Stefano's photos switched) when I updated the website. Have
pushed a fix to master.

--Richard

On Thu, Apr 5, 2018 at 7:07 PM, Balay, Satish  wrote:

> On Fri, 6 Apr 2018, Richard Tran Mills wrote:
>
> > Thanks, Satish! I notice also that, in the stanza beginning "When citing
> > PETSc, please do not refer to this document", Dave May is still missing.
>
> pushed to master.
>
> > Also, that stanza still refers to version 3.7 and 2016.
>
> updated in balay/release-3.9
>
> Thanks!
> Satish
>

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

I have the following branches for today's next-tmp test.

origin/knepley/fix-dm-gmg
origin/knepley/fix-ex62-tests
origin/knepley/fix-fe-bd-integral
origin/knepley/fix-fe-vector-spaces
origin/knepley/fix-snes-ex69
origin/tisaac/feature-dmfield
origin/hzhang/iscoloring-testvalid
origin/hzhang/superlu_dist-matinertia-hermitian
origin/scott/test-harness-timing2

Karl,

The CUDA tests are hanging/timing-out more often now. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/06/examples_next_arch-cuda-double_es.log

And I did see some build where they didn't get killed due to timeout. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/examples_next_arch-cuda-double_es.log

This is on M2090.  I can see them getting stuck on es.mcs [when I run manually 
- and check with nvidia-smi]

When i run these tests manually on GTX1050 (frog.mcs) - they zip through..
Any idea why they get stuck on M2090? [more frequently than random hangs..]

thanks,
Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Fri, 6 Apr 2018, Matthew Knepley wrote:

> On Thu, Apr 5, 2018 at 10:34 PM, Satish Balay  wrote:
> 
> > On Fri, 6 Apr 2018, Matthew Knepley wrote:
> >
> > > Okay, I pushed fixes for everything I saw except:
> > >
> >
> > >   1) The weird ex56_1 bug. This is only due to feature-dmfield, and
> > > its very strange that this logic error appears on only some
> > > arches. Toby is looking at it, but it should not hold the other
> > > branches.
> >
> > Ok
> > >  2) The restart problem for ex12. This involves something I do not
> > >   understand about the test system, namely leaving files for another
> > >   test. Again, this does not happen everywhere, and the error is
> > >   just a missing file.
> >
> > Some of these test requirements are satisfied by a small subset of
> > builds [so they don't get run in all the tests]
> >
> > >
> > > >> >   origin/knepley/fix-dm-gmg
> > > >> >   origin/knepley/fix-ex62-tests
> > > >> >   origin/knepley/fix-fe-bd-integral
> > > >> >   origin/knepley/fix-fe-vector-spaces
> > > >> >   origin/knepley/fix-snes-ex69
> > > >> >   origin/tisaac/feature-dmfield
> >
> > I can try out a quick build of your branches on a few arches. [i.e
> > with all the above branches except  'origin/tisaac/feature-dmfield']
> 
> 
> Looks like Toby fixed this 2min ago.

Ok - will run the test on master+all the above and update you.

Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Matthew Knepley]

On Thu, Apr 5, 2018 at 10:34 PM, Satish Balay  wrote:

> On Fri, 6 Apr 2018, Matthew Knepley wrote:
>
> > Okay, I pushed fixes for everything I saw except:
> >
>
> >   1) The weird ex56_1 bug. This is only due to feature-dmfield, and
> > its very strange that this logic error appears on only some
> > arches. Toby is looking at it, but it should not hold the other
> > branches.
>
> Ok
> >  2) The restart problem for ex12. This involves something I do not
> >   understand about the test system, namely leaving files for another
> >   test. Again, this does not happen everywhere, and the error is
> >   just a missing file.
>
> Some of these test requirements are satisfied by a small subset of
> builds [so they don't get run in all the tests]
>
> >
> > >> >   origin/knepley/fix-dm-gmg
> > >> >   origin/knepley/fix-ex62-tests
> > >> >   origin/knepley/fix-fe-bd-integral
> > >> >   origin/knepley/fix-fe-vector-spaces
> > >> >   origin/knepley/fix-snes-ex69
> > >> >   origin/tisaac/feature-dmfield
>
> I can try out a quick build of your branches on a few arches. [i.e
> with all the above branches except  'origin/tisaac/feature-dmfield']


Looks like Toby fixed this 2min ago.

  Matt


>
> Satish
>
>


-- 
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/ 

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Fri, 6 Apr 2018, Matthew Knepley wrote:

> Okay, I pushed fixes for everything I saw except:
> 

>   1) The weird ex56_1 bug. This is only due to feature-dmfield, and
> its very strange that this logic error appears on only some
> arches. Toby is looking at it, but it should not hold the other
> branches.

Ok
>  2) The restart problem for ex12. This involves something I do not
>   understand about the test system, namely leaving files for another
>   test. Again, this does not happen everywhere, and the error is
>   just a missing file.

Some of these test requirements are satisfied by a small subset of
builds [so they don't get run in all the tests]

> 
> >> >   origin/knepley/fix-dm-gmg
> >> >   origin/knepley/fix-ex62-tests
> >> >   origin/knepley/fix-fe-bd-integral
> >> >   origin/knepley/fix-fe-vector-spaces
> >> >   origin/knepley/fix-snes-ex69
> >> >   origin/tisaac/feature-dmfield

I can try out a quick build of your branches on a few arches. [i.e
with all the above branches except  'origin/tisaac/feature-dmfield']

Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Matthew Knepley]

On Thu, Apr 5, 2018 at 9:05 AM, Matthew Knepley  wrote:

> On Thu, Apr 5, 2018 at 8:58 AM, Satish Balay  wrote:
>
>> All,
>>
>> master builds have been clean for the past 2 days [except for some
>> timeouts]
>>
>> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/
>> 04/04/master.html
>>
>> However next is still not clean [slightly better than previous build]
>>
>> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html
>
>
> I think I know all the fixes. I cannot do it until tonight at the
> earliest. One of them,
> FETIDP, is an indentation fix.
>

Okay, I pushed fixes for everything I saw except:

  1) The weird ex56_1 bug. This is only due to feature-dmfield, and its
very strange that this
  logic error appears on only some arches. Toby is looking at it, but
it should not hold
  the other branches.

  2) The restart problem for ex12. This involves something I do not
understand about the test
   system, namely leaving files for another test. Again, this does not
happen everywhere, and
   the error is just a missing file.

  Matt



>   Thanks,
>
> Matt
>
>
>>
>> [i.e the following branches still need fixes]
>> >   origin/knepley/fix-dm-gmg
>> >   origin/knepley/fix-ex62-tests
>> >   origin/knepley/fix-fe-bd-integral
>> >   origin/knepley/fix-fe-vector-spaces
>> >   origin/knepley/fix-snes-ex69
>> >   origin/tisaac/feature-dmfield
>>
>> I have the following branches in queue for master [via next-tmp - these
>> builds will start soon]
>>
>>  origin/balay/update-petsc4py-pre-39
>>  origin/dalcinl/mat-getset-ops
>>  origin/jczhang/fix-vecscatter-msg-logging
>>
>> If next-tmp is clean - I can spin the release tarball later today [after
>> merging them to master]
>>
>> Or if there are other branches [that are clean] - that should go into
>> release - let me know.  We'll either have to wait one more day [for
>> these branches to go through next/next-tmp - or I can schedule another
>> next-tmp build later today (with additional branches) - if they are
>> ready by 3:30pm CST]
>>
>> If I do not hear back about additional branches, and next-tmp is clean
>> - will spin the release tarball later today.
>>
>> Thanks,
>> Satish
>>
>>
>
>
> --
> 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/ 
>



-- 
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/ 

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Fri, 6 Apr 2018, Richard Tran Mills wrote:

> Thanks, Satish! I notice also that, in the stanza beginning "When citing
> PETSc, please do not refer to this document", Dave May is still missing.

pushed to master.

> Also, that stanza still refers to version 3.7 and 2016.

updated in balay/release-3.9

Thanks!
Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Richard Tran Mills]

Thanks, Satish! I notice also that, in the stanza beginning "When citing
PETSc, please do not refer to this document", Dave May is still missing.
Also, that stanza still refers to version 3.7 and 2016.

--Richard

On Thu, Apr 5, 2018 at 6:26 PM, Balay, Satish  wrote:

> Thanks! I pushed some fixes to rmills/doc-add-rmills-to-user-manual.
>
> Satish
>
> On Fri, 6 Apr 2018, Richard Tran Mills wrote:
>
> > Hi Satish,
> >
> > I decided that I don't have time to polish things as much as I'd like, so
> > I'll make the significant user manual edit I had in mind after the
> release.
> > It's something that can wait.
> >
> > I do have some minor doc changes to go into master for the release. I've
> > tested these on my laptop to make sure they didn't break building the
> > manual or man pages, but I suppose you should do a doc build cycle.
> Please
> > merge in
> >
> > rmills/doc-rmills-performance-section-minor-edit
> > rmills/doc-update-matcreateseqaijmkl-man-page
> >
> > With Barry's permission, I also made changes on these branches to add
> > myself to the user manual author list and the website:
> >
> > rmills/doc-add-rmills-to-user-manual
> > rmills/webpage-add-rmills
> >
> > Could you please make sure that I made edits in all the right places for
> > the above two branches, and then merge in for the release?
> >
> > Thanks,
> > Richard
> >
> > On Thu, Apr 5, 2018 at 1:04 PM, Balay, Satish  wrote:
> >
> > > Sure - we can push doc changes without going through the test cycle
> [just
> > > a doc build cycle]
> > >
> > > thanks,
> > > Satish
> > >
> > > On Thu, 5 Apr 2018, Richard Tran Mills wrote:
> > >
> > > > Hi Satish,
> > > >
> > > > I'm working on right now on some edits to part of the "Performance
> > > Turning"
> > > > part of the manual. If I can get these edits to a state I'm happy
> with,
> > > I'd
> > > > like them to go in the release, but I'm not sure if I will have them
> > > ready
> > > > before this evening.
> > > >
> > > > --Richard
> > > >
> > > > On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish 
> wrote:
> > > >
> > > > > All,
> > > > >
> > > > > master builds have been clean for the past 2 days [except for some
> > > > > timeouts]
> > > > >
> > > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > > > > 2018/04/04/master.html
> > > > >
> > > > > However next is still not clean [slightly better than previous
> build]
> > > > >
> > > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > > 2018/04/05/next.html
> > > > >
> > > > > [i.e the following branches still need fixes]
> > > > > >   origin/knepley/fix-dm-gmg
> > > > > >   origin/knepley/fix-ex62-tests
> > > > > >   origin/knepley/fix-fe-bd-integral
> > > > > >   origin/knepley/fix-fe-vector-spaces
> > > > > >   origin/knepley/fix-snes-ex69
> > > > > >   origin/tisaac/feature-dmfield
> > > > >
> > > > > I have the following branches in queue for master [via next-tmp -
> these
> > > > > builds will start soon]
> > > > >
> > > > >  origin/balay/update-petsc4py-pre-39
> > > > >  origin/dalcinl/mat-getset-ops
> > > > >  origin/jczhang/fix-vecscatter-msg-logging
> > > > >
> > > > > If next-tmp is clean - I can spin the release tarball later today
> > > [after
> > > > > merging them to master]
> > > > >
> > > > > Or if there are other branches [that are clean] - that should go
> into
> > > > > release - let me know.  We'll either have to wait one more day [for
> > > > > these branches to go through next/next-tmp - or I can schedule
> another
> > > > > next-tmp build later today (with additional branches) - if they are
> > > > > ready by 3:30pm CST]
> > > > >
> > > > > If I do not hear back about additional branches, and next-tmp is
> clean
> > > > > - will spin the release tarball later today.
> > > > >
> > > > > Thanks,
> > > > > Satish
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

Thanks! I pushed some fixes to rmills/doc-add-rmills-to-user-manual.

Satish

On Fri, 6 Apr 2018, Richard Tran Mills wrote:

> Hi Satish,
> 
> I decided that I don't have time to polish things as much as I'd like, so
> I'll make the significant user manual edit I had in mind after the release.
> It's something that can wait.
> 
> I do have some minor doc changes to go into master for the release. I've
> tested these on my laptop to make sure they didn't break building the
> manual or man pages, but I suppose you should do a doc build cycle. Please
> merge in
> 
> rmills/doc-rmills-performance-section-minor-edit
> rmills/doc-update-matcreateseqaijmkl-man-page
> 
> With Barry's permission, I also made changes on these branches to add
> myself to the user manual author list and the website:
> 
> rmills/doc-add-rmills-to-user-manual
> rmills/webpage-add-rmills
> 
> Could you please make sure that I made edits in all the right places for
> the above two branches, and then merge in for the release?
> 
> Thanks,
> Richard
> 
> On Thu, Apr 5, 2018 at 1:04 PM, Balay, Satish  wrote:
> 
> > Sure - we can push doc changes without going through the test cycle [just
> > a doc build cycle]
> >
> > thanks,
> > Satish
> >
> > On Thu, 5 Apr 2018, Richard Tran Mills wrote:
> >
> > > Hi Satish,
> > >
> > > I'm working on right now on some edits to part of the "Performance
> > Turning"
> > > part of the manual. If I can get these edits to a state I'm happy with,
> > I'd
> > > like them to go in the release, but I'm not sure if I will have them
> > ready
> > > before this evening.
> > >
> > > --Richard
> > >
> > > On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish  wrote:
> > >
> > > > All,
> > > >
> > > > master builds have been clean for the past 2 days [except for some
> > > > timeouts]
> > > >
> > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > > > 2018/04/04/master.html
> > > >
> > > > However next is still not clean [slightly better than previous build]
> > > >
> > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > 2018/04/05/next.html
> > > >
> > > > [i.e the following branches still need fixes]
> > > > >   origin/knepley/fix-dm-gmg
> > > > >   origin/knepley/fix-ex62-tests
> > > > >   origin/knepley/fix-fe-bd-integral
> > > > >   origin/knepley/fix-fe-vector-spaces
> > > > >   origin/knepley/fix-snes-ex69
> > > > >   origin/tisaac/feature-dmfield
> > > >
> > > > I have the following branches in queue for master [via next-tmp - these
> > > > builds will start soon]
> > > >
> > > >  origin/balay/update-petsc4py-pre-39
> > > >  origin/dalcinl/mat-getset-ops
> > > >  origin/jczhang/fix-vecscatter-msg-logging
> > > >
> > > > If next-tmp is clean - I can spin the release tarball later today
> > [after
> > > > merging them to master]
> > > >
> > > > Or if there are other branches [that are clean] - that should go into
> > > > release - let me know.  We'll either have to wait one more day [for
> > > > these branches to go through next/next-tmp - or I can schedule another
> > > > next-tmp build later today (with additional branches) - if they are
> > > > ready by 3:30pm CST]
> > > >
> > > > If I do not hear back about additional branches, and next-tmp is clean
> > > > - will spin the release tarball later today.
> > > >
> > > > Thanks,
> > > > Satish
> > > >
> > > >
> > >
> >
> >
> 

Re: [petsc-dev] upcoming release and testing [v2]

[Richard Tran Mills]

Hi Satish,

I decided that I don't have time to polish things as much as I'd like, so
I'll make the significant user manual edit I had in mind after the release.
It's something that can wait.

I do have some minor doc changes to go into master for the release. I've
tested these on my laptop to make sure they didn't break building the
manual or man pages, but I suppose you should do a doc build cycle. Please
merge in

rmills/doc-rmills-performance-section-minor-edit
rmills/doc-update-matcreateseqaijmkl-man-page

With Barry's permission, I also made changes on these branches to add
myself to the user manual author list and the website:

rmills/doc-add-rmills-to-user-manual
rmills/webpage-add-rmills

Could you please make sure that I made edits in all the right places for
the above two branches, and then merge in for the release?

Thanks,
Richard

On Thu, Apr 5, 2018 at 1:04 PM, Balay, Satish  wrote:

> Sure - we can push doc changes without going through the test cycle [just
> a doc build cycle]
>
> thanks,
> Satish
>
> On Thu, 5 Apr 2018, Richard Tran Mills wrote:
>
> > Hi Satish,
> >
> > I'm working on right now on some edits to part of the "Performance
> Turning"
> > part of the manual. If I can get these edits to a state I'm happy with,
> I'd
> > like them to go in the release, but I'm not sure if I will have them
> ready
> > before this evening.
> >
> > --Richard
> >
> > On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish  wrote:
> >
> > > All,
> > >
> > > master builds have been clean for the past 2 days [except for some
> > > timeouts]
> > >
> > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > > 2018/04/04/master.html
> > >
> > > However next is still not clean [slightly better than previous build]
> > >
> > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/05/next.html
> > >
> > > [i.e the following branches still need fixes]
> > > >   origin/knepley/fix-dm-gmg
> > > >   origin/knepley/fix-ex62-tests
> > > >   origin/knepley/fix-fe-bd-integral
> > > >   origin/knepley/fix-fe-vector-spaces
> > > >   origin/knepley/fix-snes-ex69
> > > >   origin/tisaac/feature-dmfield
> > >
> > > I have the following branches in queue for master [via next-tmp - these
> > > builds will start soon]
> > >
> > >  origin/balay/update-petsc4py-pre-39
> > >  origin/dalcinl/mat-getset-ops
> > >  origin/jczhang/fix-vecscatter-msg-logging
> > >
> > > If next-tmp is clean - I can spin the release tarball later today
> [after
> > > merging them to master]
> > >
> > > Or if there are other branches [that are clean] - that should go into
> > > release - let me know.  We'll either have to wait one more day [for
> > > these branches to go through next/next-tmp - or I can schedule another
> > > next-tmp build later today (with additional branches) - if they are
> > > ready by 3:30pm CST]
> > >
> > > If I do not hear back about additional branches, and next-tmp is clean
> > > - will spin the release tarball later today.
> > >
> > > Thanks,
> > > Satish
> > >
> > >
> >
>
>

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Thu, 5 Apr 2018, Satish Balay wrote:

> I have the following branches in queue for master [via next-tmp - these 
> builds will start soon]
> 
>  origin/balay/update-petsc4py-pre-39
>  origin/dalcinl/mat-getset-ops
>  origin/jczhang/fix-vecscatter-msg-logging
> 
> If next-tmp is clean - I can spin the release tarball later today [after 
> merging them to master]

These are now merged to master.

Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

Sure - we can push doc changes without going through the test cycle [just a doc 
build cycle]

thanks,
Satish

On Thu, 5 Apr 2018, Richard Tran Mills wrote:

> Hi Satish,
> 
> I'm working on right now on some edits to part of the "Performance Turning"
> part of the manual. If I can get these edits to a state I'm happy with, I'd
> like them to go in the release, but I'm not sure if I will have them ready
> before this evening.
> 
> --Richard
> 
> On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish  wrote:
> 
> > All,
> >
> > master builds have been clean for the past 2 days [except for some
> > timeouts]
> >
> > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> > 2018/04/04/master.html
> >
> > However next is still not clean [slightly better than previous build]
> >
> > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html
> >
> > [i.e the following branches still need fixes]
> > >   origin/knepley/fix-dm-gmg
> > >   origin/knepley/fix-ex62-tests
> > >   origin/knepley/fix-fe-bd-integral
> > >   origin/knepley/fix-fe-vector-spaces
> > >   origin/knepley/fix-snes-ex69
> > >   origin/tisaac/feature-dmfield
> >
> > I have the following branches in queue for master [via next-tmp - these
> > builds will start soon]
> >
> >  origin/balay/update-petsc4py-pre-39
> >  origin/dalcinl/mat-getset-ops
> >  origin/jczhang/fix-vecscatter-msg-logging
> >
> > If next-tmp is clean - I can spin the release tarball later today [after
> > merging them to master]
> >
> > Or if there are other branches [that are clean] - that should go into
> > release - let me know.  We'll either have to wait one more day [for
> > these branches to go through next/next-tmp - or I can schedule another
> > next-tmp build later today (with additional branches) - if they are
> > ready by 3:30pm CST]
> >
> > If I do not hear back about additional branches, and next-tmp is clean
> > - will spin the release tarball later today.
> >
> > Thanks,
> > Satish
> >
> >
> 

Re: [petsc-dev] upcoming release and testing [v2]

[Richard Tran Mills]

Hi Satish,

I'm working on right now on some edits to part of the "Performance Turning"
part of the manual. If I can get these edits to a state I'm happy with, I'd
like them to go in the release, but I'm not sure if I will have them ready
before this evening.

--Richard

On Thu, Apr 5, 2018 at 5:58 AM, Balay, Satish  wrote:

> All,
>
> master builds have been clean for the past 2 days [except for some
> timeouts]
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/04/master.html
>
> However next is still not clean [slightly better than previous build]
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html
>
> [i.e the following branches still need fixes]
> >   origin/knepley/fix-dm-gmg
> >   origin/knepley/fix-ex62-tests
> >   origin/knepley/fix-fe-bd-integral
> >   origin/knepley/fix-fe-vector-spaces
> >   origin/knepley/fix-snes-ex69
> >   origin/tisaac/feature-dmfield
>
> I have the following branches in queue for master [via next-tmp - these
> builds will start soon]
>
>  origin/balay/update-petsc4py-pre-39
>  origin/dalcinl/mat-getset-ops
>  origin/jczhang/fix-vecscatter-msg-logging
>
> If next-tmp is clean - I can spin the release tarball later today [after
> merging them to master]
>
> Or if there are other branches [that are clean] - that should go into
> release - let me know.  We'll either have to wait one more day [for
> these branches to go through next/next-tmp - or I can schedule another
> next-tmp build later today (with additional branches) - if they are
> ready by 3:30pm CST]
>
> If I do not hear back about additional branches, and next-tmp is clean
> - will spin the release tarball later today.
>
> Thanks,
> Satish
>
>

Re: [petsc-dev] upcoming release and testing [v2]

[Matthew Knepley]

On Thu, Apr 5, 2018 at 9:28 AM, Satish Balay  wrote:

> On Thu, 5 Apr 2018, Matthew Knepley wrote:
>
> > >
> > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/05/next.html
> >
> > I think I know all the fixes. I cannot do it until tonight at the
> earliest.
> > One of them, FETIDP, is an indentation fix.
>
> Once the fixes are in - I think it will take a few iterations [i.e a
> few test cycles] to verify them [ and fix missing issues].
>
> So assuming all fixes are pushed by tonight - [and you are able to
> check build logs and fix issues immediately - and reschedule tests
> immediately - we could do the release later tomorrow [but it might
> push over to weekend/early-next week].
>
> 1. Are few fix cycles by tomorrow feasible? [Matt]
>

Maybe, not sure


> 2. Do these branches need to go into the release? [Matt]
>

No, it senseless to push it, but I do want a clean next as soon as we can.

   Matt


> 3. Is it ok if the release gets pushed to early next week? [Barry, Todd]
>
> [assuming currently scheduled branches in next-tmp will be clean]
>
> thanks,
> Satish
>
> > > [i.e the following branches still need fixes]
> > > >   origin/knepley/fix-dm-gmg
> > > >   origin/knepley/fix-ex62-tests
> > > >   origin/knepley/fix-fe-bd-integral
> > > >   origin/knepley/fix-fe-vector-spaces
> > > >   origin/knepley/fix-snes-ex69
> > > >   origin/tisaac/feature-dmfield
>



-- 
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/ 

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

Thanks! Added patch to master.

Satish

On Thu, 5 Apr 2018, Patrick Sanan wrote:

> Spellcheck fixes for dev.html :
> 
> - relavant --> relevant
> - diffencing --> differencing
> - seperately --> separately
> 
> Patch also attached.
> 
> 2018-04-05 17:03 GMT+02:00 Satish Balay :
> 
> > Thanks Karl!
> >
> > BTW: Its best to update dev.html in master [and then I can rebase
> > balay/release-3.9 over master. This way - the commit in
> > balay/release-3.9 is the final commit for the release - and traceable
> > later]
> >
> > So i've moved this commit over to master.
> >
> > Satish
> >
> > On Thu, 5 Apr 2018, Karl Rupp wrote:
> >
> > > Hi Satish,
> > >
> > > FYI: I added a mention of GPU backends available in the release and fixed
> > > missing ul-tags in src/docs/website/documentation/changes/39.html in
> > your
> > > balay/release-3.9 branch.
> > >
> > > Best regards,
> > > Karli
> > >
> > > On 04/02/2018 08:18 PM, Satish Balay wrote:
> > > > All,
> > > >
> > > > It would be good if
> > > > http://www.mcs.anl.gov/petsc/documentation/changes/dev.html is cheked
> > and
> > > > updated with any obvious missing stuff.
> > > >
> > > > Thanks,
> > > > Satish
> > > >
> > >
> >
> >
> 

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

Thanks! merged to master.

Satish

On Thu, 5 Apr 2018, Zhang, Hong wrote:

> Hi Satish,
> 
> I have just updated the dev changes in the branch hongzh/update-dev.
> 
> Regards,
> Hong (Mr.)
> 
> > On Apr 2, 2018, at 12:18 PM, Satish Balay  wrote:
> > 
> > All,
> > 
> > It would be good if 
> > http://www.mcs.anl.gov/petsc/documentation/changes/dev.html is cheked and 
> > updated with any obvious missing stuff.
> > 
> > Thanks,
> > Satish
> 
> 

Re: [petsc-dev] upcoming release and testing

[Zhang, Hong]

Hi Satish,

I have just updated the dev changes in the branch hongzh/update-dev.

Regards,
Hong (Mr.)

> On Apr 2, 2018, at 12:18 PM, Satish Balay  wrote:
> 
> All,
> 
> It would be good if 
> http://www.mcs.anl.gov/petsc/documentation/changes/dev.html is cheked and 
> updated with any obvious missing stuff.
> 
> Thanks,
> Satish

Re: [petsc-dev] upcoming release and testing

[Patrick Sanan]

Spellcheck fixes for dev.html :

- relavant --> relevant
- diffencing --> differencing
- seperately --> separately

Patch also attached.

2018-04-05 17:03 GMT+02:00 Satish Balay :

> Thanks Karl!
>
> BTW: Its best to update dev.html in master [and then I can rebase
> balay/release-3.9 over master. This way - the commit in
> balay/release-3.9 is the final commit for the release - and traceable
> later]
>
> So i've moved this commit over to master.
>
> Satish
>
> On Thu, 5 Apr 2018, Karl Rupp wrote:
>
> > Hi Satish,
> >
> > FYI: I added a mention of GPU backends available in the release and fixed
> > missing ul-tags in src/docs/website/documentation/changes/39.html in
> your
> > balay/release-3.9 branch.
> >
> > Best regards,
> > Karli
> >
> > On 04/02/2018 08:18 PM, Satish Balay wrote:
> > > All,
> > >
> > > It would be good if
> > > http://www.mcs.anl.gov/petsc/documentation/changes/dev.html is cheked
> and
> > > updated with any obvious missing stuff.
> > >
> > > Thanks,
> > > Satish
> > >
> >
>
>


0001-Docs-dev-changes-typos.patch
Description: Binary data

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

Thanks Karl!

BTW: Its best to update dev.html in master [and then I can rebase
balay/release-3.9 over master. This way - the commit in
balay/release-3.9 is the final commit for the release - and traceable
later]

So i've moved this commit over to master.

Satish

On Thu, 5 Apr 2018, Karl Rupp wrote:

> Hi Satish,
> 
> FYI: I added a mention of GPU backends available in the release and fixed
> missing ul-tags in src/docs/website/documentation/changes/39.html in your
> balay/release-3.9 branch.
> 
> Best regards,
> Karli
> 
> On 04/02/2018 08:18 PM, Satish Balay wrote:
> > All,
> > 
> > It would be good if
> > http://www.mcs.anl.gov/petsc/documentation/changes/dev.html is cheked and
> > updated with any obvious missing stuff.
> > 
> > Thanks,
> > Satish
> > 
> 

Re: [petsc-dev] upcoming release and testing

[Karl Rupp]

Hi Satish,

FYI: I added a mention of GPU backends available in the release and 
fixed missing ul-tags in src/docs/website/documentation/changes/39.html 
in your balay/release-3.9 branch.


Best regards,
Karli

On 04/02/2018 08:18 PM, Satish Balay wrote:

All,

It would be good if http://www.mcs.anl.gov/petsc/documentation/changes/dev.html 
is cheked and updated with any obvious missing stuff.

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Thu, 5 Apr 2018, Matthew Knepley wrote:

> >
> > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html
> 
> I think I know all the fixes. I cannot do it until tonight at the earliest.
> One of them, FETIDP, is an indentation fix.

Once the fixes are in - I think it will take a few iterations [i.e a
few test cycles] to verify them [ and fix missing issues].

So assuming all fixes are pushed by tonight - [and you are able to
check build logs and fix issues immediately - and reschedule tests
immediately - we could do the release later tomorrow [but it might
push over to weekend/early-next week].

1. Are few fix cycles by tomorrow feasible? [Matt]

2. Do these branches need to go into the release? [Matt]

3. Is it ok if the release gets pushed to early next week? [Barry, Todd]

[assuming currently scheduled branches in next-tmp will be clean]

thanks,
Satish

> > [i.e the following branches still need fixes]
> > >   origin/knepley/fix-dm-gmg
> > >   origin/knepley/fix-ex62-tests
> > >   origin/knepley/fix-fe-bd-integral
> > >   origin/knepley/fix-fe-vector-spaces
> > >   origin/knepley/fix-snes-ex69
> > >   origin/tisaac/feature-dmfield

Re: [petsc-dev] upcoming release and testing [v2]

[Matthew Knepley]

On Thu, Apr 5, 2018 at 8:58 AM, Satish Balay  wrote:

> All,
>
> master builds have been clean for the past 2 days [except for some
> timeouts]
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/04/master.html
>
> However next is still not clean [slightly better than previous build]
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html


I think I know all the fixes. I cannot do it until tonight at the earliest.
One of them,
FETIDP, is an indentation fix.

  Thanks,

Matt


>
> [i.e the following branches still need fixes]
> >   origin/knepley/fix-dm-gmg
> >   origin/knepley/fix-ex62-tests
> >   origin/knepley/fix-fe-bd-integral
> >   origin/knepley/fix-fe-vector-spaces
> >   origin/knepley/fix-snes-ex69
> >   origin/tisaac/feature-dmfield
>
> I have the following branches in queue for master [via next-tmp - these
> builds will start soon]
>
>  origin/balay/update-petsc4py-pre-39
>  origin/dalcinl/mat-getset-ops
>  origin/jczhang/fix-vecscatter-msg-logging
>
> If next-tmp is clean - I can spin the release tarball later today [after
> merging them to master]
>
> Or if there are other branches [that are clean] - that should go into
> release - let me know.  We'll either have to wait one more day [for
> these branches to go through next/next-tmp - or I can schedule another
> next-tmp build later today (with additional branches) - if they are
> ready by 3:30pm CST]
>
> If I do not hear back about additional branches, and next-tmp is clean
> - will spin the release tarball later today.
>
> Thanks,
> Satish
>
>


-- 
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/ 

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

All,

master builds have been clean for the past 2 days [except for some timeouts]

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/04/master.html

However next is still not clean [slightly better than previous build]

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/next.html

[i.e the following branches still need fixes]
>   origin/knepley/fix-dm-gmg
>   origin/knepley/fix-ex62-tests
>   origin/knepley/fix-fe-bd-integral
>   origin/knepley/fix-fe-vector-spaces
>   origin/knepley/fix-snes-ex69
>   origin/tisaac/feature-dmfield

I have the following branches in queue for master [via next-tmp - these builds 
will start soon]

 origin/balay/update-petsc4py-pre-39
 origin/dalcinl/mat-getset-ops
 origin/jczhang/fix-vecscatter-msg-logging

If next-tmp is clean - I can spin the release tarball later today [after 
merging them to master]

Or if there are other branches [that are clean] - that should go into
release - let me know.  We'll either have to wait one more day [for
these branches to go through next/next-tmp - or I can schedule another
next-tmp build later today (with additional branches) - if they are
ready by 3:30pm CST]

If I do not hear back about additional branches, and next-tmp is clean
- will spin the release tarball later today.

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

On Wed, 4 Apr 2018, Satish Balay wrote:

> I have the following branches in queue for master [via next-tmp - this build 
> will start now]
> 
>   origin/dalcinl/fix-scatter-destroy
>   origin/dalcinl/fix-vecscatter-initpkg
>   origin/knepley/fix-cylinder-mesh
>   origin/rmills/feature-aijmkl-add-matptap-symmetric
>   origin/barry/removed-unneeded-mpi-comm-dup-boomeramg
>   origin/balay/fix-9bus-ex9busdmnetwork-chkstk-on-windows
>   origin/jed/futurize-stage-1

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/04/next-tmp.html

next-tmp builds are clean [except for a few example timeouts] - so I merged 
them all to master.

Satish

Re: [petsc-dev] upcoming release and testing [v2]

[Satish Balay]

FYI - I have the release related strings in 
https://bitbucket.org/petsc/petsc/branch/balay/release-3.9

This change should be similar to what was done for 3.8 release

https://bitbucket.org/petsc/petsc/commits/0e50f9e530a7b78427514d3e384f6941d4a9cc62?at=v3.8

For now - I'm using tomorrow's date [but will update it when we are ready to do 
the release]

This branch will be rebased as needed.

Satish

[petsc-dev] upcoming release and testing [v2]

[Satish Balay]

[starting a new thread]

As of now master builds are clean!

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/03/master.html

next is improved but still has issues that need fixing.

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/04/next.html

most-likely are are related to the following branches [and some 
dependencies/conflicts with changes in master]

  origin/knepley/fix-dm-gmg
  origin/knepley/fix-ex62-tests
  origin/knepley/fix-fe-bd-integral
  origin/knepley/fix-fe-vector-spaces
  origin/knepley/fix-snes-ex69
  origin/tisaac/feature-dmfield

I have the following branches in queue for master [via next-tmp - this build 
will start now]

  origin/dalcinl/fix-scatter-destroy
  origin/dalcinl/fix-vecscatter-initpkg
  origin/knepley/fix-cylinder-mesh
  origin/rmills/feature-aijmkl-add-matptap-symmetric
  origin/barry/removed-unneeded-mpi-comm-dup-boomeramg
  origin/balay/fix-9bus-ex9busdmnetwork-chkstk-on-windows
  origin/jed/futurize-stage-1


1. If there are any other branches/PRs that should go into the release - let me 
know
2. reminder - please check and update 
src/docs/website/documentation/changes/dev.html [or send me diffs]

Thanks!
Satish

Re: [petsc-dev] upcoming release and testing

[Karl Rupp]

Hi Satish,

CUDA and ViennaCL can be enabled for the first time in this release.

Best regards,
Karli



On 04/02/2018 08:15 PM, Satish Balay wrote:

Karl,

Are we disabling CUDA usage for this release aswell?

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Mon, 2 Apr 2018, Satish Balay wrote:

> On Mon, 2 Apr 2018, Satish Balay wrote:
> 
> > Thanks! updated knepley/fix-ex62-tests and merged to next-tmp
> 
> next-tmp has plenty of errors..

Forgot to include the dashboard url

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/02/next-tmp.html

Satish

> 
> It currently has:
> origin/knepley/fix-ex62-tests
> origin/knepley/fix-dm-gmg
> origin/knepley/fix-cylinder-mesh
> origin/dalcinl/fix-scatter-destroy
> origin/dalcinl/fix-vecscatter-initpkg
> origin/balay/update-openmpi-3.0.1
> 
> So I don't [yet] know which of these branches are causing grief - and
> which ones are ok - so I can't merge any of them to master..
> 
> Satish
> 

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Mon, 2 Apr 2018, Satish Balay wrote:

> Thanks! updated knepley/fix-ex62-tests and merged to next-tmp

next-tmp has plenty of errors..

It currently has:
origin/knepley/fix-ex62-tests
origin/knepley/fix-dm-gmg
origin/knepley/fix-cylinder-mesh
origin/dalcinl/fix-scatter-destroy
origin/dalcinl/fix-vecscatter-initpkg
origin/balay/update-openmpi-3.0.1

So I don't [yet] know which of these branches are causing grief - and
which ones are ok - so I can't merge any of them to master..

Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

All,

It would be good if http://www.mcs.anl.gov/petsc/documentation/changes/dev.html 
is cheked and updated with any obvious missing stuff.

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

Karl,

Are we disabling CUDA usage for this release aswell?

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

I had pushed this change yesterday.

Satish

On Mon, 2 Apr 2018, Smith, Barry F. wrote:

> 
>   Satish,
> 
> This happens on that one machine where it produces MUCH less precision 
> then for any other block size or machine configuration. I investigated a 
> little when it first happened and my guess is there some issue with the 
> compiler producing "bad" code on this one system.
> 
> I hate to have an alt file for a buggy compiler but don't have any other 
> suggestion go ahead and add the alt file.
> 
>   Barry
> 
> 
> > On Apr 1, 2018, at 12:08 PM, Balay, Satish  wrote:
> > 
> > On Sun, 1 Apr 2018, Satish Balay wrote:
> > 
> >> I'll try to send follow up emails on master brakages.
> > 
> > Barry,
> > 
> > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-cuda-single_es.log
> > 
> > not ok diff-ksp_ksp_tests-ex49_1_bs-7
> > #   0a1
> > #   > Norm of residual 0.00159951 iterations 2 bs 7
> > 
> > This came up on 2018/01/24 - I think - from migrating from old to new 
> > testsuite. How to fix? Add alt output file?
> > 
> > 
> > diff --git a/src/ksp/ksp/examples/tests/output/ex49_1_alt.out 
> > b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> > new file mode 100644
> > index 000..828d9d9
> > --- /dev/null
> > +++ b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> > @@ -0,0 +1 @@
> > +Norm of residual 0.00159951 iterations 2 bs 7
> > 
> > 
> > Thanks,
> > Satish
> > 
> > 
> 
> 

Re: [petsc-dev] upcoming release and testing

[Smith, Barry F.]

  Satish,

This happens on that one machine where it produces MUCH less precision then 
for any other block size or machine configuration. I investigated a little when 
it first happened and my guess is there some issue with the compiler producing 
"bad" code on this one system.

I hate to have an alt file for a buggy compiler but don't have any other 
suggestion go ahead and add the alt file.

  Barry


> On Apr 1, 2018, at 12:08 PM, Balay, Satish  wrote:
> 
> On Sun, 1 Apr 2018, Satish Balay wrote:
> 
>> I'll try to send follow up emails on master brakages.
> 
> Barry,
> 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-cuda-single_es.log
> 
> not ok diff-ksp_ksp_tests-ex49_1_bs-7
> # 0a1
> # > Norm of residual 0.00159951 iterations 2 bs 7
> 
> This came up on 2018/01/24 - I think - from migrating from old to new 
> testsuite. How to fix? Add alt output file?
> 
> 
> diff --git a/src/ksp/ksp/examples/tests/output/ex49_1_alt.out 
> b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> new file mode 100644
> index 000..828d9d9
> --- /dev/null
> +++ b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> @@ -0,0 +1 @@
> +Norm of residual 0.00159951 iterations 2 bs 7
> 
> 
> Thanks,
> Satish
> 
> 

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Mon, 2 Apr 2018, Matthew Knepley wrote:

> > not ok diff-snes_tutorials-ex62_23
> > #   5c5
> > #   <   total number of linear solver iterations=11
> > #   ---
> > #   >   total number of linear solver iterations=12
> >
> 
> Ah, test 23 is missing
> 
> filter:  sed -e "s/total number of linear solver iterations=11/total
> number of linear solver iterations=12/g"
> 
> I can put it in the branch, or you can if its faster then me.

Thanks! updated knepley/fix-ex62-tests and merged to next-tmp

Satish

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Matthew Knepley]

On Mon, Apr 2, 2018 at 10:02 AM, Satish Balay  wrote:

> On Mon, 2 Apr 2018, Matthew Knepley wrote:
>
> >
> > origin/knepley/fix-cylinder-mesh
> > origin/knepley/fix-dm-gmg
> > origin/knepley/fix-ex62-tests
> >
> > should all go clean. Can we try those in next-tmp whenever you have a
> > chance.
> >
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/02/examples_full_next.log
>
> has stuff like:
>
> not ok diff-snes_tutorials-ex62_23
> #   5c5
> #   <   total number of linear solver iterations=11
> #   ---
> #   >   total number of linear solver iterations=12
>

Ah, test 23 is missing

filter:  sed -e "s/total number of linear solver iterations=11/total
number of linear solver iterations=12/g"

I can put it in the branch, or you can if its faster then me.

  Thanks,

Matt


> I've merged them to next-tmp which are currently in progress - so they
> will miss stage-1 builds [out of 4 stages]
>
> Satish
>



-- 
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/ 

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Mon, 2 Apr 2018, Matthew Knepley wrote:

> 
> origin/knepley/fix-cylinder-mesh
> origin/knepley/fix-dm-gmg
> origin/knepley/fix-ex62-tests
> 
> should all go clean. Can we try those in next-tmp whenever you have a
> chance.
> 
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/02/examples_full_next.log

has stuff like:

not ok diff-snes_tutorials-ex62_23
#   5c5
#   <   total number of linear solver iterations=11
#   ---
#   >   total number of linear solver iterations=12

I've merged them to next-tmp which are currently in progress - so they will 
miss stage-1 builds [out of 4 stages]

Satish

Re: [petsc-dev] upcoming release and testing

[Matthew Knepley]

On Sun, Apr 1, 2018 at 5:12 PM, Satish Balay  wrote:

>
> I've merged the following branches [tested in next-tmp] to master.
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/04/01/next-tmp.html
>
> origin/jed/fix-analyzer-bugs
> origin/balay/update-hypre-v2.14.0
> origin/denera/tao-lmvm-info-bugfix
> origin/knepley/feature-med-pkg
> origin/knepley/fix-hdf5-attribute
> origin/knepley/test-allow-line-continuation
> origin/balay/update-zoltan-v3.83
>

Great.


> The outstanding branches in next are:
>
>   origin/knepley/fix-cylinder-mesh
>   origin/knepley/fix-dm-gmg
>   origin/knepley/fix-ex62-tests
>   origin/knepley/fix-fe-bd-integral
>   origin/knepley/fix-fe-vector-spaces
>   origin/knepley/fix-snes-ex69
>   origin/tisaac/feature-dmfield
>

origin/knepley/fix-cylinder-mesh
origin/knepley/fix-dm-gmg
origin/knepley/fix-ex62-tests

should all go clean. Can we try those in next-tmp whenever you have a
chance.


> So any issues in 'next' that are not in 'master' are likely due to these
> branches.
>
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/01/next.html
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/
> 2018/03/31/master.html
>
> Matt, Toby - can you take a look at these issues?
>

Yes.

  Thanks,

 Matt


> If needed - we can schedule one branch at a time in next-tmp testing.
>
> Thanks,
> Satish
>



-- 
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/ 

Re: [petsc-dev] upcoming release and testing

[Karl Rupp]

Hi Satish,


I'll try to send follow up emails on master brakages.


Karl,

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-c-exodus-dbg-builder_es.log

not ok ksp_ksp_tests-ex43_1
#   terminate called after throwing an instance of 
'thrust::system::system_error'
# what():  cudaFree in free: an illegal memory access was encountered


Is this related to cuda change? [I haven't explored yet]


this looks like a one-off test failure. The previous day that test ran 
through. Also, I only removed CUSP stuff, but did not alter the existing 
CUDA backend.


Best regards,
Karli

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

I've merged the following branches [tested in next-tmp] to master.

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/01/next-tmp.html

origin/jed/fix-analyzer-bugs
origin/balay/update-hypre-v2.14.0
origin/denera/tao-lmvm-info-bugfix
origin/knepley/feature-med-pkg
origin/knepley/fix-hdf5-attribute
origin/knepley/test-allow-line-continuation
origin/balay/update-zoltan-v3.83

The outstanding branches in next are:

  origin/knepley/fix-cylinder-mesh
  origin/knepley/fix-dm-gmg
  origin/knepley/fix-ex62-tests
  origin/knepley/fix-fe-bd-integral
  origin/knepley/fix-fe-vector-spaces
  origin/knepley/fix-snes-ex69
  origin/tisaac/feature-dmfield

So any issues in 'next' that are not in 'master' are likely due to these 
branches.

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/01/next.html
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/master.html

Matt, Toby - can you take a look at these issues?
If needed - we can schedule one branch at a time in next-tmp testing.

Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Sun, 1 Apr 2018, Satish Balay wrote:

> On Sun, 1 Apr 2018, Satish Balay wrote:
> 
> > I'll try to send follow up emails on master brakages.
> 
> Barry,
> 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-cuda-single_es.log
> 
> not ok diff-ksp_ksp_tests-ex49_1_bs-7
> # 0a1
> # > Norm of residual 0.00159951 iterations 2 bs 7
> 
> This came up on 2018/01/24 - I think - from migrating from old to new 
> testsuite. How to fix? Add alt output file?
> 
> 
> diff --git a/src/ksp/ksp/examples/tests/output/ex49_1_alt.out 
> b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> new file mode 100644
> index 000..828d9d9
> --- /dev/null
> +++ b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
> @@ -0,0 +1 @@
> +Norm of residual 0.00159951 iterations 2 bs 7


pushed this fix.

Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Sun, 1 Apr 2018, Satish Balay wrote:

> I'll try to send follow up emails on master brakages.

Barry,

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-cuda-single_es.log

not ok diff-ksp_ksp_tests-ex49_1_bs-7
#   0a1
#   > Norm of residual 0.00159951 iterations 2 bs 7

This came up on 2018/01/24 - I think - from migrating from old to new 
testsuite. How to fix? Add alt output file?


diff --git a/src/ksp/ksp/examples/tests/output/ex49_1_alt.out 
b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
new file mode 100644
index 000..828d9d9
--- /dev/null
+++ b/src/ksp/ksp/examples/tests/output/ex49_1_alt.out
@@ -0,0 +1 @@
+Norm of residual 0.00159951 iterations 2 bs 7


Thanks,
Satish

Re: [petsc-dev] upcoming release and testing

[Blaise A Bourdin]

Hi Satish,

I am working on it. ex26 tests a bunch of DMPlex functions which I don’t think 
are tested anywhere else. The test itself may also have leaks.

Blaise


> On Apr 1, 2018, at 11:42 AM, Satish Balay  wrote:
> 
> On Sun, 1 Apr 2018, Satish Balay wrote:
> 
>> I'll try to send follow up emails on master brakages.
> 
> Blaise,
> 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-c-exodus-dbg-builder_es.log
> 
> dm_impls_plex_tests-ex26 has bunch of memory leaks and diffs. I could track 
> one of the memory leaks to f94b4a023f1c697a53e49ac853a9031583ab9737 -  but 
> don't know what the trigger is - or how to fix it.
> 
> not ok diff-dm_impls_plex_tests-ex26_6
> # 969a970,2569
> # > [ 0]16 bytes PetscSFBasicGetPack() line 806 in 
> /sandbox/petsc/petsc.master-3/src/vec/is/sf/impls/basic/sfbasic.c
> # >   [0]  PetscMallocA() line 806 in 
> /sandbox/petsc/petsc.master-3/src/sys/memory/mal.c
> # >   [0]  PetscSFBasicGetPack() line 778 in 
> /sandbox/petsc/petsc.master-3/src/vec/is/sf/impls/basic/sfbasic.c
> # >   [0]  PetscSFBcastBegin_Basic() line 923 in 
> /sandbox/petsc/petsc.master-3/src/vec/is/sf/impls/basic/sfbasic.c
> # >   [0]  PetscSFBcastBegin() line 1045 in 
> /sandbox/petsc/petsc.master-3/src/vec/is/sf/interface/sf.c
> # >   [0]  DMPlexGlobalToNaturalBegin() line 183 in 
> /sandbox/petsc/petsc.master-3/src/dm/impls/plex/plexnatural.c
> # >   [0]  VecViewPlex_ExodusII_Zonal_Internal() line 678 in 
> /sandbox/petsc/petsc.master-3/src/dm/impls/plex/plexexodusii.c
> 
> And there are diffs which should be checked..
> 
> not ok diff-dm_impls_plex_tests-ex26_7
> # 536c536
> # <   Cell Sets: 2 strata with value/size (3 (9), 5 (9))
> # ---
> # >   Cell Sets: 2 strata with value/size (1 (9), 2 (9))
> # 537a538,2137
> 
> not ok diff-dm_impls_plex_tests-ex26_10
> # 536c536
> # <   Cell Sets: 2 strata with value/size (3 (9), 5 (9))
> # ---
> # >   Cell Sets: 2 strata with value/size (1 (9), 2 (9))
> # 537a538,2137
> 
> 
> # <   0-cells: 28 36
> # <   1-cells: 58 67
> # ---
> # >   0-cells: 34 32
> # >   1-cells: 64 63
> # 734,735c734,2335
> # <   Cell Sets: 3 strata with value/size (2 (1), 3 (28), 5 (3))
> # <   depth: 3 strata with value/size (0 (28), 1 (58), 2 (32))
> # ---
> # >   Cell Sets: 3 strata with value/size (1 (9), 2 (18), 3 (5))
> # >   depth: 3 strata with value/size (0 (34), 1 (64), 2 (32))
> 
> etc..
> 
> thanks,
> Satish
> 

-- 
Department of Mathematics and Center for Computation & Technology
Louisiana State University, Baton Rouge, LA 70803, USA
Tel. +1 (225) 578 1612, Fax  +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin

Re: [petsc-dev] upcoming release and testing

[Smith, Barry F.]

   Everyone,

  I think this model is way to labor intense on Satish to keep permanently 
but we'll keep it to get past the release and then rethink the model. Satish is 
also working to decrease the test time so we can hopefully open up more testing 
slots. My dream is each person gets a testing slot for themselves but this is 
not likely in the short term so we may have a small number of people share each 
testing slot.

 Barry


> On Apr 1, 2018, at 11:24 AM, Satish Balay  wrote:
> 
> PETSc developers,
> 
> I've change daily/nightly tests to have 3 tests every day [from the current 2 
> tests]:
> 
> - next
> - next-tmp [can change this test slot as needed]
> - master
> 
> Please note the time/schedule of these tests 
> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/
> 
> next; run everyday 12am to 7:30am Chicago time
> next-tmp; run everyday 8am to 3:30pm
> master; run weekdays 4pm to 11:30pm
> 
> [I haven't yet added back 'maint' - will do it at some point]
> 
> Plan is to test branches in next-tmp before merge to master so:
> 
> Please do *not* merge any feature branches from next to master without 
> additional testing via next-tmp.
> 
> If you think a branch is ready for merge - let me know - and I'll schedule it 
> into next-tmp
> 
> Also - please look at breakages in master [without a clean master - its 
> difficult to know when feature branches in next/next-tmp are clean. And when 
> feature branches from dirty next are merged to master - master gets more 
> broke]
> 
> I'll try to send follow up emails on master brakages.
> 
> Notes about next-tmp:
> 
> - for now only I have push access to it [so that I can test selected feature 
> branches with it, and reset it as needed]
> 
> - it will be 'latest-master + a few test branches' and updated with 'push -f' 
> [i.e not a continuously updated branch like next]
> 
> Thanks,
> Satish

Re: [petsc-dev] upcoming release and testing

[Satish Balay]

On Sun, 1 Apr 2018, Satish Balay wrote:

> I'll try to send follow up emails on master brakages.

Karl,

http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/03/31/examples_master_arch-c-exodus-dbg-builder_es.log

not ok ksp_ksp_tests-ex43_1
#   terminate called after throwing an instance of 
'thrust::system::system_error'
# what():  cudaFree in free: an illegal memory access was encountered


Is this related to cuda change? [I haven't explored yet]

Satish

[petsc-dev] upcoming release and testing

[Satish Balay]

PETSc developers,

I've change daily/nightly tests to have 3 tests every day [from the current 2 
tests]:

- next
- next-tmp [can change this test slot as needed]
- master

Please note the time/schedule of these tests 
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/

next; run everyday 12am to 7:30am Chicago time
next-tmp; run everyday 8am to 3:30pm
master; run weekdays 4pm to 11:30pm

[I haven't yet added back 'maint' - will do it at some point]

Plan is to test branches in next-tmp before merge to master so:

Please do *not* merge any feature branches from next to master without 
additional testing via next-tmp.

If you think a branch is ready for merge - let me know - and I'll schedule it 
into next-tmp

Also - please look at breakages in master [without a clean master - its 
difficult to know when feature branches in next/next-tmp are clean. And when 
feature branches from dirty next are merged to master - master gets more broke]

I'll try to send follow up emails on master brakages.

Notes about next-tmp:

- for now only I have push access to it [so that I can test selected feature 
branches with it, and reset it as needed]

- it will be 'latest-master + a few test branches' and updated with 'push -f' 
[i.e not a continuously updated branch like next]

Thanks,
Satish