[petsc-dev] error with karlrupp/fix-cuda-streams

Mark Adams mfadams at lbl.gov
Thu Sep 26 09:10:48 CDT 2019


Karl, I have it running but I am not seeing any difference from master. I
wonder if I have the right version:

Using Petsc Development GIT revision: v3.11.3-2207-ga8e311a

I could not find karlrupp/fix-cuda-streams on the gitlab page to check your
last commit SHA1 (???), and now I get:

08:37 karlrupp/fix-cuda-streams= ~/petsc-karl$ git pull origin
karlrupp/fix-cuda-streams
fatal: Couldn't find remote ref karlrupp/fix-cuda-streams
Unexpected end of command stream
10:09 1 karlrupp/fix-cuda-streams= ~/petsc-karl$



On Wed, Sep 25, 2019 at 8:51 AM Karl Rupp <rupp at iue.tuwien.ac.at> wrote:

>
> > I double checked that a clean build of your (master) branch has this
> > error by my branch (mark/fix-cuda-with-gamg-pintocpu), which may include
> > stuff from Barry that is not yet in master, works.
>
> so did master work recently (i.e. right before my branch got merged)?
>
> Best regards,
> Karli
>
>
>
> >
> > On Wed, Sep 25, 2019 at 5:26 AM Karl Rupp via petsc-dev
> > <petsc-dev at mcs.anl.gov <mailto:petsc-dev at mcs.anl.gov>> wrote:
> >
> >
> >
> >     On 9/25/19 11:12 AM, Mark Adams via petsc-dev wrote:
> >      > I am using karlrupp/fix-cuda-streams, merged with master, and I
> >     get this
> >      > error:
> >      >
> >      > Could not execute "['jsrun -g\\ 1 -c\\ 1 -a\\ 1 --oversubscribe
> -n 1
> >      > printenv']":
> >      > Error, invalid argument:  1
> >      >
> >      > My branch mark/fix-cuda-with-gamg-pintocpu seems to work but I
> >     did edit
> >      > the jsrun command but Karl's branch still fails. (SUMMIT was down
> >     today
> >      > so there could have been updates).
> >      >
> >      > Any suggestions?
> >
> >     Looks very much like a systems issue to me.
> >
> >     Best regards,
> >     Karli
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190926/b20686fe/attachment.html>


More information about the petsc-dev mailing list