On Wed, Sep 25, 2019 at 6:23 PM Balay, Satish <ba...@mcs.anl.gov> wrote:
> > 18:16 (cb53a04...) ~/petsc-karl$
>
> So this is the commit I recommended you test against - and that's what
> you have got now. Please go ahead and test.
>
>
I sent the log for this. This is the output:
18:16 (cb53a04...) ~/petsc-karl$ ../arch-summit-opt64idx-pgi-cuda.py
PETSC_DIR=$PWD
===============================================================================
Configuring PETSc to compile on your system
===============================================================================
===============================================================================
***** WARNING: F77 (set to
/autofs/nccs-svm1_sw/summit/.swci/0-core/opt/spack/20180914/linux-rhel7-ppc64le/gcc-4.8.5/pgi-19.4-6acz4xyqjlpoaonjiiqjme2aknrfnzoy/linux
use ./configure F77=$F77 if you really want to use that value ******
===============================================================================
===============================================================================
***** WARNING: Using default optimization C flags -O
You might consider manually setting
optimal optimization flags for your system with
COPTFLAGS="optimization flags" see config/examples/arch-*-opt.py for
examples
===============================================================================
===============================================================================
***** WARNING: You have an older version of Gnu make,
it will work,
but may not support all the
parallel testing options. You can install the
latest
Gnu make with your package manager, such as brew or macports, or use
the --download-make option to get the latest Gnu make warning
message *****
===============================================================================
TESTING: configureMPIEXEC from
config.packages.MPI(config/BuildSystem/config/packages/MPI.py:174)
*******************************************************************************
UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for
details):
-------------------------------------------------------------------------------
Unable to run jsrun -g 1 with option "-n 1"
Error: It is only possible to use js commands within a job allocation
unless CSM is running
09-25-2019 18:20:13:224 108023 main: Error initializing RM connection.
Exiting.
*******************************************************************************
18:20 1 (cb53a04...) ~/petsc-karl$
> [note: the branch is rebased - so 'git pull' won't work -(as you can
> see from the "(forced update)" message - and '<>' status from git
> prompt on balay/fix-mpiexec-shell-escape). So perhaps its easier to
> deal with in detached mode - which makes this obvious]
>
I got this <> and "fixed" it by deleting the branch and repulling it. I
guess I needed to fetch also.
Mark
>
> Satish
>
>
> On Wed, 25 Sep 2019, Mark Adams via petsc-dev wrote:
>
> > I will test this now but ....
> >
> > 17:52 balay/fix-mpiexec-shell-escape= ~/petsc-karl$ git fetch
> > remote: Enumerating objects: 119, done.
> > remote: Counting objects: 100% (119/119), done.
> > remote: Compressing objects: 100% (91/91), done.
> > remote: Total 119 (delta 49), reused 74 (delta 28)
> > Receiving objects: 100% (119/119), 132.88 KiB | 0 bytes/s, done.
> > Resolving deltas: 100% (49/49), completed with 1 local objects.
> > >From https://gitlab.com/petsc/petsc
> > + b5e99a5...cb53a04 balay/fix-mpiexec-shell-escape ->
> > origin/balay/fix-mpiexec-shell-escape (forced update)
> > + ffdc635...7eeb5f9 jczhang/feature-sf-on-gpu ->
> > origin/jczhang/feature-sf-on-gpu (forced update)
> > cb9de97..f9ff08a jolivet/fix-error-col-row ->
> > origin/jolivet/fix-error-col-row
> > 40ea605..de5ad60 oanam/jacobf/cell-to-ref-mapping ->
> > origin/oanam/jacobf/cell-to-ref-mapping
> > + ecac953...9fb579e stefanozampini/hypre-cuda-rebased ->
> > origin/stefanozampini/hypre-cuda-rebased (forced update)
> > 18:16 balay/fix-mpiexec-shell-escape<> ~/petsc-karl$ git checkout
> > origin/balay/fix-mpiexec-shell-escape
> > Note: checking out 'origin/balay/fix-mpiexec-shell-escape'.
> >
> > You are in 'detached HEAD' state. You can look around, make experimental
> > changes and commit them, and you can discard any commits you make in this
> > state without impacting any branches by performing another checkout.
> >
> > If you want to create a new branch to retain commits you create, you may
> > do so (now or later) by using -b with the checkout command again.
> Example:
> >
> > git checkout -b new_branch_name
> >
> > HEAD is now at cb53a04... mpiexec: fix shell escape of path-to-mpiexec
> only
> > when using autodected-path. Also spectrum MPI uses OMPI_MAJOR_VERSION
> etc -
> > so check if mpiexec supports --oversubscribe - before using it.
> > 18:16 (cb53a04...) ~/petsc-karl$
> >
> > On Wed, Sep 25, 2019 at 5:58 PM Balay, Satish <ba...@mcs.anl.gov> wrote:
> >
> > > Defined "VERSION_GIT" to ""v3.11.3-2242-gb5e99a5""
> > >
> > > This is not the latest state - It should be:
> > >
> > > commit cb53a042369fb946804f53931a88b58e10588da1 (HEAD ->
> > > balay/fix-mpiexec-shell-escape, origin/balay/fix-mpiexec-shell-escape)
> > >
> > > Try:
> > >
> > > git fetch
> > > git checkout origin/balay/fix-mpiexec-shell-escape
> > >
> > > Satish
> > >
> > > On Wed, 25 Sep 2019, Mark Adams via petsc-dev wrote:
> > >
> > > > On Wed, Sep 25, 2019 at 4:57 PM Balay, Satish <ba...@mcs.anl.gov>
> wrote:
> > > >
> > > > > On Wed, 25 Sep 2019, Mark Adams via petsc-dev wrote:
> > > > >
> > > > > > I did test this and sent the log (error).
> > > > >
> > > > > Mark,
> > > > >
> > > > > I made more changes - can you retry again - and resend log.
> > > > >
> > > > > Satish
> > > > >
> > > >
> > >
> > >
> >
>
>
