[petsc-dev] ?????? Petsc: Error code 1

Dear Professor?? Attachment is the alltests.log file. Best, Gang ---- ??: "petsc-dev"

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

> > > Generically, independent of Kokkos, ideally I would run a single > precompiled NVIDIA program that gave me all the information about the > current hardware I was running and that would provide in simple format > exactly the information I needed to configure PETSc, Kokkos etc for THAT >

Re: [petsc-dev] Petsc: Error code 1

Note: do not use '-j' with alltests. And run alltests on both machines [but *not* at the same time on machines] and send us logs from both the runs. Satish On Mon, 5 Apr 2021, Satish Balay wrote: > Try: > > make alltests TIMEOUT=600 > > And send us the complete log (alltests.log) > >

Re: [petsc-dev] Petsc: Error code 1

Try: make alltests TIMEOUT=600 And send us the complete log (alltests.log) Satish On Tue, 6 Apr 2021, Chen Gang wrote: > Dear sir, > > > The result of make check is OK. And I do set the timeout to a larger value, > which keeps me from getting timeout error. The thing is I have two

Re: [petsc-dev] Petsc: Error code 1

Dear sir, The result of make check is OK. And I do set the timeout to a larger value, which keeps me from getting timeout error. The thing is I have two machines. And I get the error code 1 in different tests on different machines.I don’t know what is error code1. What case this? How can I

Re: [petsc-dev] Petsc: Error code 1

To check the install - we suggest: make check 'make test' runs the full test suite. Note the test suite is parallel - so if using '-j' the multiple parallel jobs can overload the machine and slow things down. So best to use a much smaller -j value, and with a larger timeout. make -j4 test

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

Junchao, I hope my latest MRs manages that for the current generation of those values. If not, we need refinement. Barry > On Apr 5, 2021, at 9:30 PM, Junchao Zhang wrote: > > > > > On Mon, Apr 5, 2021 at 7:33 PM Jeff Hammond > wrote: > NVCC has

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

Thanks Jeff, The information is eventually there somewhere, the issue is more getting the information in a simple way, automatically, at PETSc configure time that is portable and will never crash. https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__DEVICE.html

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

On Mon, Apr 5, 2021 at 7:33 PM Jeff Hammond wrote: > NVCC has supported multi-versioned "fat" binaries since I worked for > Argonne. Libraries should figure out what the oldest hardware they are > about is and then compile for everything from that point forward. Kepler > (3.5) is oldest

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

NVCC has supported multi-versioned "fat" binaries since I worked for Argonne. Libraries should figure out what the oldest hardware they are about is and then compile for everything from that point forward. Kepler (3.5) is oldest version any reasonable person should be thinking about at this

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

This is nvidia mess-up. Why isn't there a command that give me these values [if they insist on this interface for nvcc] I see Barry want configure to do something here - but whatever we do - we would be shifting the problem around. [even if we detect stuff - build box might not have the GPU

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

Hmm, OK, I found a table at https://sparta.sandia.gov/doc/accelerate_kokkos.html and it tells me that "PASCAL60" refers to "NVIDIA Pascal generation CC 6.0 GPU" and "PASCAL61" refers to "NVIDIA Pascal generation CC 6.1 GPU". But I have no idea what those 6.0 vs 6.1 version numbers mean, and

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

You raise a good point, Barry. I've been completely mystified by what some of these names even mean. What does "PASCAL60" vs. "PASCAL61" even mean? Do you know of where this is even documented? I can't really find anything about it in the Kokkos documentation. The only thing I can really find

[petsc-dev] DMNetwork static sizing

Dowe really need a configure time constant for struct _p_DMNetworkComponentHeader { PetscInt index;/* index for user input global edge and vertex */ PetscInt subnetid; /* Id for subnetwork */ PetscInt ndata;/* number of components */ PetscInt