April 2018 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] upcoming release and testing [v2]
by Satish Balay 05 Apr '18

05 Apr '18

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 <balay(a)mcs.anl.gov> 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 <balay(a)mcs.anl.gov> 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 > > > > > > > > > > > > > > > >

1 0

Re: [petsc-dev] upcoming release and testing [v2]
by Richard Tran Mills 05 Apr '18

05 Apr '18

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 <balay(a)mcs.anl.gov> 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 <balay(a)mcs.anl.gov> 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 > > > > > > > > > >

1 0

CMake
by Matthew Knepley 05 Apr '18

05 Apr '18

Can we remove all packages that use CMake before the next release? See also "/PETSc3/petsc/petsc-pylith/arch-next-debug/externalpackages/hg.eigen/build/CMakeFiles/CMakeOutput.log".CMake Error at /PETSc3/petsc/petsc-pylith/arch-pylith-debug/share/cmake-3.0/Modules/Platform/Darwin.cmake:211 (message): CMAKE_OSX_DEPLOYMENT_TARGET is '10.5' but CMAKE_OSX_SYSROOT: "" is not set to a MacOSX SDK with a recognized version. Either set CMAKE_OSX_SYSROOT to a valid SDK or set CMAKE_OSX_DEPLOYMENT_TARGET to empty. I hate them. Matt -- 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/ <http://www.caam.rice.edu/~mk51/>

1 0

Re: [petsc-dev] [petsc-users] ftp.mcs.anl.gov is down - breaking petsc builds with --download-package
by Derek Gaston 05 Apr '18

05 Apr '18

Thanks for getting back to me - must be something about my environment here (ftp might even be blocked currently - although I did try from two different networks). I was able to get what I needed by using "http" for now. Sorry for the traffic. Derek On Thu, Apr 5, 2018 at 4:54 PM Satish Balay <balay(a)mcs.anl.gov> wrote: > Both ftp and http work fine for me.. > > balay@asterix /home/balay/petsc.x/petsc (balay/test=) > $ lftp ftp://ftp.mcs.anl.gov/pub/petsc/externalpackages > cd ok, cwd=/pub/petsc/externalpackages > lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> ls |head > -rw-r----- 1 ftp ftp 0 Nov 18 2016 ==33186== > -rw-r----- 1 ftp ftp 828346 May 2 2013 Chaco-2.2-p1.tar.gz > -rw-r----- 1 ftp ftp 1981220 Sep 23 2014 Chaco-2.2-p2.tar.gz > -rw-r----- 1 ftp ftp 828295 Oct 23 2009 Chaco-2.2.tar.gz > -rw-r----- 1 ftp ftp 1685576 Feb 16 2015 > Elemental-0.85-p1.tar.gz > -rw-r----- 1 ftp ftp 112597 Mar 28 2012 Generator.tar.gz > -rw-r----- 1 ftp ftp 2471411 Nov 18 2011 > MUMPS_4.10.0-p1.tar.gz > -rw-r----- 1 ftp ftp 2471465 Feb 26 2012 > MUMPS_4.10.0-p2.tar.gz > -rw-r----- 1 ftp ftp 2440565 Mar 15 2012 > MUMPS_4.10.0-p3.tar.gz > -rw-r----- 1 ftp ftp 2439922 Aug 17 2011 MUMPS_4.10.0.tar.gz > lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> exit > balay@asterix /home/balay/petsc.x/petsc (balay/test=) > $ lftp http://ftp.mcs.anl.gov/pub/petsc/externalpackages > cd: received redirection to ` > http://ftp.mcs.anl.gov/pub/petsc/externalpackages/' > cd ok, cwd=/pub/petsc/externalpackages > lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> ls |head > drwxr-xr-x -- .. > -rw-r--r-- 0 2016-11-18 11:03 ==33186== > -rw-r--r-- 809K 2013-05-01 22:00 Chaco-2.2-p1.tar.gz > -rw-r--r-- 1.9M 2014-09-23 13:52 Chaco-2.2-p2.tar.gz > -rw-r--r-- 809K 2009-10-22 19:53 Chaco-2.2.tar.gz > -rw-r--r-- 1.6M 2015-02-16 14:21 Elemental-0.85-p1.tar.gz > -rw-r--r-- 110K 2012-03-27 19:22 Generator.tar.gz > -rw-r--r-- 2.4M 2011-11-18 13:59 MUMPS_4.10.0-p1.tar.gz > -rw-r--r-- 2.4M 2012-02-25 21:05 MUMPS_4.10.0-p2.tar.gz > -rw-r--r-- 2.3M 2012-03-14 22:57 MUMPS_4.10.0-p3.tar.gz > ls: Broken pipe > lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> exit > > > Satish > > On Thu, 5 Apr 2018, Derek Gaston wrote: > > > Is ftp access down again? The download links on the PETSc website appear > > to just stall... > > > > Derek > > > > On Thu, Mar 29, 2018 at 9:52 AM Satish Balay <balay(a)mcs.anl.gov> wrote: > > > > > ftp.mcs.anl.gov is now back online [serving ftp:// - http:// is not > yet > > > enabled] > > > > > > petsc configure builds with --download-package option should now work. > > > > > > For direct tarball download - switching the URL from > > > http://ftp.mcs.anl.gov to ftp://ftp.mcs.anl.gov notation is the > > > temporary workaround. For eg: > > > > > > change: > > > http://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > > > to: > > > ftp://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > > > > > > Satish > > > > > > On Thu, 29 Mar 2018, Satish Balay wrote: > > > > > > > > > > > We've been informed by the site admin that ftp.mcs.anl.gov is taken > > > > down due to 'cyber incident' - there is no ETA on when it will be > > > > back. > > > > > > > > We've been using it the primary host for distributing petsc tarballs > > > > and hosting some externalpackage tarballs - so some of the petsc > buils > > > > with '--download-package' option are failing. > > > > > > > > Obtaining petsc [and some most externalpackages] via git should work. > > > > > > > > I will update when ftp.mcs.anl.gov is brought back up. > > > > > > > > Satish > > > > > > > > > > > > > > > > > >

1 0

Re: [petsc-dev] [petsc-users] ftp.mcs.anl.gov is down - breaking petsc builds with --download-package
by Satish Balay 05 Apr '18

05 Apr '18

Both ftp and http work fine for me.. balay@asterix /home/balay/petsc.x/petsc (balay/test=) $ lftp ftp://ftp.mcs.anl.gov/pub/petsc/externalpackages cd ok, cwd=/pub/petsc/externalpackages lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> ls |head -rw-r----- 1 ftp ftp 0 Nov 18 2016 ==33186== -rw-r----- 1 ftp ftp 828346 May 2 2013 Chaco-2.2-p1.tar.gz -rw-r----- 1 ftp ftp 1981220 Sep 23 2014 Chaco-2.2-p2.tar.gz -rw-r----- 1 ftp ftp 828295 Oct 23 2009 Chaco-2.2.tar.gz -rw-r----- 1 ftp ftp 1685576 Feb 16 2015 Elemental-0.85-p1.tar.gz -rw-r----- 1 ftp ftp 112597 Mar 28 2012 Generator.tar.gz -rw-r----- 1 ftp ftp 2471411 Nov 18 2011 MUMPS_4.10.0-p1.tar.gz -rw-r----- 1 ftp ftp 2471465 Feb 26 2012 MUMPS_4.10.0-p2.tar.gz -rw-r----- 1 ftp ftp 2440565 Mar 15 2012 MUMPS_4.10.0-p3.tar.gz -rw-r----- 1 ftp ftp 2439922 Aug 17 2011 MUMPS_4.10.0.tar.gz lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> exit balay@asterix /home/balay/petsc.x/petsc (balay/test=) $ lftp http://ftp.mcs.anl.gov/pub/petsc/externalpackages cd: received redirection to `http://ftp.mcs.anl.gov/pub/petsc/externalpackages/' cd ok, cwd=/pub/petsc/externalpackages lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> ls |head drwxr-xr-x -- .. -rw-r--r-- 0 2016-11-18 11:03 ==33186== -rw-r--r-- 809K 2013-05-01 22:00 Chaco-2.2-p1.tar.gz -rw-r--r-- 1.9M 2014-09-23 13:52 Chaco-2.2-p2.tar.gz -rw-r--r-- 809K 2009-10-22 19:53 Chaco-2.2.tar.gz -rw-r--r-- 1.6M 2015-02-16 14:21 Elemental-0.85-p1.tar.gz -rw-r--r-- 110K 2012-03-27 19:22 Generator.tar.gz -rw-r--r-- 2.4M 2011-11-18 13:59 MUMPS_4.10.0-p1.tar.gz -rw-r--r-- 2.4M 2012-02-25 21:05 MUMPS_4.10.0-p2.tar.gz -rw-r--r-- 2.3M 2012-03-14 22:57 MUMPS_4.10.0-p3.tar.gz ls: Broken pipe lftp ftp.mcs.anl.gov:/pub/petsc/externalpackages> exit Satish On Thu, 5 Apr 2018, Derek Gaston wrote: > Is ftp access down again? The download links on the PETSc website appear > to just stall... > > Derek > > On Thu, Mar 29, 2018 at 9:52 AM Satish Balay <balay(a)mcs.anl.gov> wrote: > > > ftp.mcs.anl.gov is now back online [serving ftp:// - http:// is not yet > > enabled] > > > > petsc configure builds with --download-package option should now work. > > > > For direct tarball download - switching the URL from > > http://ftp.mcs.anl.gov to ftp://ftp.mcs.anl.gov notation is the > > temporary workaround. For eg: > > > > change: > > http://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > > to: > > ftp://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > > > > Satish > > > > On Thu, 29 Mar 2018, Satish Balay wrote: > > > > > > > > We've been informed by the site admin that ftp.mcs.anl.gov is taken > > > down due to 'cyber incident' - there is no ETA on when it will be > > > back. > > > > > > We've been using it the primary host for distributing petsc tarballs > > > and hosting some externalpackage tarballs - so some of the petsc buils > > > with '--download-package' option are failing. > > > > > > Obtaining petsc [and some most externalpackages] via git should work. > > > > > > I will update when ftp.mcs.anl.gov is brought back up. > > > > > > Satish > > > > > > > > > > >

1 0

Re: [petsc-dev] [petsc-users] ftp.mcs.anl.gov is down - breaking petsc builds with --download-package
by Derek Gaston 05 Apr '18

05 Apr '18

Is ftp access down again? The download links on the PETSc website appear to just stall... Derek On Thu, Mar 29, 2018 at 9:52 AM Satish Balay <balay(a)mcs.anl.gov> wrote: > ftp.mcs.anl.gov is now back online [serving ftp:// - http:// is not yet > enabled] > > petsc configure builds with --download-package option should now work. > > For direct tarball download - switching the URL from > http://ftp.mcs.anl.gov to ftp://ftp.mcs.anl.gov notation is the > temporary workaround. For eg: > > change: > http://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > to: > ftp://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.8.4.tar.gz > > Satish > > On Thu, 29 Mar 2018, Satish Balay wrote: > > > > > We've been informed by the site admin that ftp.mcs.anl.gov is taken > > down due to 'cyber incident' - there is no ETA on when it will be > > back. > > > > We've been using it the primary host for distributing petsc tarballs > > and hosting some externalpackage tarballs - so some of the petsc buils > > with '--download-package' option are failing. > > > > Obtaining petsc [and some most externalpackages] via git should work. > > > > I will update when ftp.mcs.anl.gov is brought back up. > > > > Satish > > > > > >

1 0

Re: [petsc-dev] upcoming release and testing [v2]
by Satish Balay 05 Apr '18

05 Apr '18

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

1 0

Re: [petsc-dev] upcoming release and testing [v2]
by Satish Balay 05 Apr '18

05 Apr '18

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 <balay(a)mcs.anl.gov> 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 > > > > >

1 0

Re: [petsc-dev] upcoming release and testing [v2]
by Richard Tran Mills 05 Apr '18

05 Apr '18

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 <balay(a)mcs.anl.gov> 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 > >

1 0

Re: [petsc-dev] upcoming release and testing [v2]
by Matthew Knepley 05 Apr '18

05 Apr '18

On Thu, Apr 5, 2018 at 9:28 AM, Satish Balay <balay(a)mcs.anl.gov> 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/ <http://www.caam.rice.edu/~mk51/>

1 0