[petsc-dev] CMake-assisted CUDA builds ready

Karl Rupp rupp at mcs.anl.gov
Mon Mar 25 11:10:36 CDT 2013


Hi Dave,

it was another timeout issue again. The combination of various external 
packages as well as the optimization flags provided led to a CMake boot 
time of 72 seconds on my machine, which is more than the 60 seconds 
timeout we used so far. The same timeout must have appeared on your machine.

The new timeout is now set to 300 seconds and should also be sufficient 
for weaker machines^1. Waiting in 'next' for another test run :-)

Thanks for all the testing and best regards,
Karli

^1 Except some supercomputers with OpenMP enabled... ;-)


On 03/23/2013 07:48 PM, Dave Nystrom wrote:
> Thanks.  I mistakenly sent the log files to petsc-dev.  Sorry about that.  I
> did a resend and sent them to petsc-maint.
>
> Dave
>
> Karl Rupp writes:
>   > Hi Dave,
>   >
>   > thanks for the log-files and the testing. CMake hangs during it's
>   > startup and thus runs into a timeout. Maybe this is related to the bug
>   > Jed found in CMake 2.8.10.2, I have no other explanation why this hangs.
>   > I'll try to reproduce this as soon as I' at a CUDA-enabled machine again.
>   >
>   > Best regards,
>   > Karli
>   >
>   >
>   >
>   > On 03/23/2013 06:49 PM, Dave Nystrom wrote:
>   > > Hi Karli,
>   > >
>   > > Still does not seem to work.  Attached are the logs from the latest attempt.
>   > >
>   > > Cheers,
>   > >
>   > > Dave
>   > >
>   > >
>   > >
>   > >
>   > > Karl Rupp writes:
>   > >   > Hi again,
>   > >   >
>   > >   > I've found the cause of the issue, namely an overly tight timeout during
>   > >   > the CMake initialization. Dave, could you please rerun reconfigure and
>   > >   > make in the latest `next`?
>   > >   >
>   > >   > Thanks and best regards,
>   > >   > Karli
>   > >   >
>   > >   >
>   > >   >
>   > >   > On 03/20/2013 07:31 PM, Dave Nystrom wrote:
>   > >   > > Hi Karli,
>   > >   > >
>   > >   > > Just now seeing this.  I did my build from a clean slate.
>   > >   > >
>   > >   > > Thanks,
>   > >   > >
>   > >   > > Dave
>   > >   > >
>   > >   > > Karl Rupp writes:
>   > >   > >   > Hi Dave,
>   > >   > >   >
>   > >   > >   > I also found that in some occasions one should issue
>   > >   > >   > $> rm -rf PETSC_ARCH/CMake*
>   > >   > >   > prior to running a reconfigure in order to circumvent a bug [1] in CMake.
>   > >   > >   >
>   > >   > >   > @Jed, Matt: The current cmakeboot.py removes
>   > >   > >   > PETSC_ARCH/CMakeFiles/{version_string}, which does not seem to even
>   > >   > >   > exist on my machine (CMake 2.8.7). Can we instead just delete the whole
>   > >   > >   > CMakeFiles-folder and probably CMakeCache.txt?
>   > >   > >   >
>   > >   > >   > Best regards,
>   > >   > >   > Karli
>   > >   > >   >
>   > >   > >   > [1] http://www.mail-archive.com/cmake@cmake.org/msg44765.html
>   > >   > >   >
>   > >   > >   >
>   > >   > >   >
>   > >   > >   > On 03/20/2013 10:17 AM, Nystrom, William D wrote:
>   > >   > >   > > Hi Karli,
>   > >   > >   > >
>   > >   > >   > > I ran a test build last night and it failed.  It was a relatively simple configuration where
>   > >   > >   > > I was downloading mpich and cmake and building with threads, cuda and the txpetscgpu
>   > >   > >   > > package.  I was building on a Fedora 17 machine with Cuda 5.  The failure seem to be
>   > >   > >   > > associated with cmake.  When I get home this evening, I could send you the configure
>   > >   > >   > > and make logs.  I did not have time this morning before leaving for work.  I wanted to
>   > >   > >   > > give you some early feedback even though the logs will have to wait till this evening.
>   > >   > >   > >
>   > >   > >   > > Thanks,
>   > >   > >   > >
>   > >   > >   > > Dave
>   > >   > >   > >
>   > >   > >   > > --
>   > >   > >   > > Dave Nystrom
>   > >   > >   > > LANL HPC-5
>   > >   > >   > > Phone: 505-667-7913
>   > >   > >   > > Email: wdn at lanl.gov
>   > >   > >   > > Smail: Mail Stop B272
>   > >   > >   > >         Group HPC-5
>   > >   > >   > >         Los Alamos National Laboratory
>   > >   > >   > >         Los Alamos, NM 87545
>   > >   > >   > >
>   > >   > >   > >
>   > >   > >   > > ________________________________________
>   > >   > >   > > From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on behalf of Karl Rupp [rupp at mcs.anl.gov]
>   > >   > >   > > Sent: Tuesday, March 19, 2013 4:04 PM
>   > >   > >   > > To: petsc-dev at mcs.anl.gov
>   > >   > >   > > Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready
>   > >   > >   > >
>   > >   > >   > > Hi Dave,
>   > >   > >   > >
>   > >   > >   > > perfect, thanks!
>   > >   > >   > > I should add that a reconfigure is needed. It won't work with re-running
>   > >   > >   > > make only.
>   > >   > >   > >
>   > >   > >   > > Best regards,
>   > >   > >   > > Karli
>   > >   > >   > >
>   > >   > >   > >
>   > >   > >   > > On 03/19/2013 04:59 PM, Nystrom, William D wrote:
>   > >   > >   > >> Hi Karli,
>   > >   > >   > >>
>   > >   > >   > >> I will try this soon and report back when I have results.
>   > >   > >   > >>
>   > >   > >   > >> Thanks,
>   > >   > >   > >>
>   > >   > >   > >> Dave
>   > >   > >   > >>
>   > >   > >   > >> ________________________________________
>   > >   > >   > >> From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on behalf of Karl Rupp [rupp at mcs.anl.gov]
>   > >   > >   > >> Sent: Tuesday, March 19, 2013 3:58 PM
>   > >   > >   > >> To: For users of the development version of PETSc
>   > >   > >   > >> Subject: [petsc-dev] CMake-assisted CUDA builds ready
>   > >   > >   > >>
>   > >   > >   > >> Dear all,
>   > >   > >   > >>
>   > >   > >   > >> I just merged the CMake-based builds for CUDA-packages into 'next',
>   > >   > >   > >> reducing compilation times considerably compared to the old legacy
>   > >   > >   > >> builds. While the legacy builds print something like
>   > >   > >   > >>     'libfast in <DIR>'
>   > >   > >   > >> the new CMake-based builds print the usual percentage counters in front.
>   > >   > >   > >>
>   > >   > >   > >> Any feedback on the proper functionality (both positive and negative)
>   > >   > >   > >> are appreciated.
>   > >   > >   > >>
>   > >   > >   > >> Thanks and best regards,
>   > >   > >   > >> Karli
>   > >   > >   > >>
>   > >   > >   > >
>   > >   > >   >
>   > >   > >
>   > >
>   >
>




More information about the petsc-dev mailing list