Where (e.g. on which kind of filesystem) are you trying to run ‘make
check’?
Can you kill -9 that one process and see if it proceeds to completion
on remaining tests?
Since I'm working on a serial build, right now, I'm using scratch disk
local to the node I'm doing my builds on, mounted as '/local' When I do
a control-C, the whole 'make check' process appears to end, it doesn't
go on to the next test.
I'm now doing a build with minimal options specified in the configure
step to see if maybe combinations of options was causing the problem.
For parallel tests, you *should* be using a parallel fileystem. I
frequently forget about that.
Do you mean a shared filesystem, like NFS, or a true parallel filesystem
like Lustre or GPFS? After realizing my stupidity of trying to do the
parallel make check on my local disk, I did move it to an NFS filesystem.
Prentice
On 07/25/2016 04:07 PM, Miller, Mark C. wrote:
30+mins *does* seem a bit long.
Typically, a ‘make check’ for me completes *all* tests in a total of
about 10-15 mins at the most.
Where (e.g. on which kind of filesystem) are you trying to run ‘make
check’?
For parallel tests, you *should* be using a parallel fileystem. I
frequently forget about that.
If the parallel filesystem is *extremely* busy and/or not setup to
deal with small I/Os and/or files (as the tests generate), I could see
there being *some* additional delay in completion.
The btree test I think is testing HDF5’s internal btree data
structures for group objects. So, if its doing any I/O I think its a
bunch of tiny HDF5 metadata stuff.
Can you kill -9 that one process and see if it proceeds to completion
on remaining tests?
Mark
From: Hdf-forum <[email protected]
<mailto:[email protected]>> on behalf of Prentice
Bisbal <[email protected] <mailto:[email protected]>>
Reply-To: HDF Users Discussion List <[email protected]
<mailto:[email protected]>>
Date: Monday, July 25, 2016 at 12:59 PM
To: "[email protected]
<mailto:[email protected]>" <[email protected]
<mailto:[email protected]>>
Subject: [Hdf-forum] How long should 'make check' take?
How long should make check normally take to run for a serial build?
After 'make check' was hanging for me at testphdf5 when building HDF5
with parallel support, make check now seems to be hanging when
testing
btree2. It's been at the same spot for 30 minutes or more, but this
time, I see the process (lt-btree2) using CPU and memory in top, just
not much of it. Is this normal? I would expect file I/O tests to only
take a few minutes, not 30+ minutes.
--
Prentice
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected] <mailto:[email protected]>
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5
