#2117: CarpetIOHDF5 commit 69c73fb1 " CarpetIOHDF5: Add "active" attribute to grid
function dataset describing which points are active" break 'IO::out_mode =
"onefile"'
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
Setting
{{{
IO::out_mode = "onefile"
}}}
in a parfile and running with more than 1 MPI ranks causes and out-of-
range array access in Output.cc in line 913:
{{{
ostringstream buf;
buf << (vdd.at(Carpet::map)
->local_boxes.at(mglevel)
.at(refinementlevel)
----> .at(local_component)
.active);
}}}
due to {{{local_component}}} being -1. This is the backtrace:
{{{
#6 0x00007ffff3a03355 in std::__throw_out_of_range_fmt(char const*, ...)
()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7 0x00005555578f17ee in std::vector<dh::local_dboxes,
std::allocator<dh::local_dboxes> >::_M_range_check (__n=<optimized out>,
this=<optimized out>) at /usr/include/c++/7/bits/stl_vector.h:825
#8 std::vector<dh::local_dboxes, std::allocator<dh::local_dboxes> >::at
(__n=<optimized out>,
this=<optimized out>) at /usr/include/c++/7/bits/stl_vector.h:846
#9 CarpetIOHDF5::AddAttributes (cctkGH=cctkGH@entry=0x55555f829ab0,
fullname=fullname@entry=0x5555634efb10 "TMUNUBASE::eTxx", vdim=3,
refinementlevel=<optimized out>,
refinementlevel@entry=0, request=request@entry=0x5555635801b0,
bbox=...,
dataset=360287970189640065, is_index=false)
at
/data/rhaas/postdoc/gr/cactus/ET_vanilla/configs/sim/build/CarpetIOHDF5/Output.cc:913
#10 0x00005555578f2a45 in CarpetIOHDF5::WriteVarChunkedSequential
(cctkGH=cctkGH@entry=0x55555f829ab0,
outfile=outfile@entry=72057594037928056, io_bytes=@0x7fffffffb960:
62212, request=0x5555635801b0,
called_from_checkpoint=called_from_checkpoint@entry=true,
indexfile=indexfile@entry=-1)
at
/data/rhaas/postdoc/gr/cactus/ET_vanilla/configs/sim/build/CarpetIOHDF5/Output.cc:513
#11 0x00005555578d9bdf in CarpetIOHDF5::Checkpoint (cctkGH=0x55555f829ab0,
called_from=0)
at
/data/rhaas/postdoc/gr/cactus/ET_vanilla/configs/sim/build/CarpetIOHDF5/CarpetIOHDF5.cc:1218
}}}
To reproduce:
{{{
wget https://einsteintoolkit.org/gallery/ns/tov.par
OMP_NUM_THREADS=1 mpirun -n 2 exe/cactus_sim tov.par
}}}
}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2117>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2097: Jenkins test system should use generic.cfg where possible
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: hinder
Type: enhancement | Status: new
Priority: minor | Milestone: ET_2018_02
Component: Jenkins | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
We now recommend using generic.cfg instead of OS-specific optionlists, so
the Jenkins test system should do the same.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2097>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2116: simfactory --remote does not detect incorrect options
------------------------+---------------------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version: development version
Keywords: |
------------------------+---------------------------------------------------
simfactory --remote passes the command that one wants to execute to a
remote machine. However while doing so, simfactory parses and re-builds
the command line. In the process of building the command line it will
*only* rebuild those that it recognizes and silently ignore the others.
Ie:
{{{
simfactory/bin/sim --remote bluewaters list-simulations --simfactory-does-
not-check-options
}}}
will succeed while the same command executed locally will fail.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2116>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2114: Carpet/Carpet/test/64k2.par test fails on Jenkins test machine
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
The test Carpet/Carpet/test/64k2.par exits with nonzero and reports:
{{{
INFO (Carpet): There are 0 3-dimensional grid arrays in 0 groups
INFO (Carpet): (The number of variables counts all time levels)
ERROR from host 7ce14e5707a0 process 0
while executing schedule bin (none), routine (no thorn)::(no routine)
in thorn CarpetLib, file
/home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/CarpetLib/mem.cc:113:
-> Failed to allocate 12884901888 bytes (12884.902 MB) of memory for
type CCTK_REAL8. 312 bytes (0.000 MB) are currently allocated in 39
objects
ERROR from host 7ce14e5707a0 process 0
while executing schedule bin (none), routine (no thorn)::(no routine)
in thorn CarpetLib, file
/home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/CarpetLib/mem.cc:113:
-> Failed to allocate 12884901888 bytes (12884.902 MB) of memory for
type CCTK_REAL8. 312 bytes (0.000 MB) are currently allocated in 39
objects
cactus_sim:
/home/jenkins/workspace/EinsteinToolkitGeneric/configs/sim/build/Carpet/helpers.cc:275:
int Carpet::Abort(const cGH*, int): Assertion `0' failed.
Rank 0 with PID 4507 received signal 6
Writing backtrace to 64k2/backtrace.0.txt
Aborted (core dumped)
}}}
Note that this has probably been happening for a very long time. The test
system just doesn't detect the problem (see #2113).
I'm not 100% sure what this test is supposed to do. It has
Carpet::enable_no_storage = yes, so it shouldn't be trying to allocate
memory. The test machine has 4 GB of RAM. This could be increased, but
we probably don't want to have a test in the ET that requires so much
memory.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2114>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2113: Test system ignores exit code of Cactus
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
When a test is running, and Cactus fails with a nonzero exit code, the
test system populates a data structure to indicate that the test has
failed:
{{{
RunTestUtils.pl:1618, RunTest():
$testdata->{"$thorn FAILED"} .= "$parfile ";
$testdata->{"NFAILED"}++;
}}}
but the test is later regarded as successful. Probably the function
CompareTestFiles ignores the fail code set by RunTest. In the case where
the test has data file to compare with, this usually is exhibited as a
failure, as the new files will probably not be created. But in the case
where there are no data files to compare with, the system doesn't expect
to find any, and the test succeeds. CompareTestFiles probably needs to be
modified to take into account the failed run, or maybe it should never be
called in the first place.
The test Carpet/Carpet/test/64k2.par currently shows this problem; it
reports that it is unable to allocate 12 GB of RAM, and exits like this:
{{{
------------------------------------------------------------------------
Test Carpet: 64k2
"Carpet/Carpet/test/64k2.par"
Issuing rm -f output-0000-active && ln -s . output-0000-active && mkdir
-p SIMFACTORY &&
TESTSUITE_PARFILE=/home/jenkins/workspace/simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/arrangements/Carpet/Carpet/test/64k2.par
/home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/SIMFACTORY/RunScript
Cactus exited with error code 134
Please check the logfile
/home/jenkins/workspace/simulations/EinsteinToolkit_f297f2e499015361358e5acfe294e024673292e3_1/output-0000/TEST/sim/Carpet/64k2.log
No files created in test directory
Success: 0 files identical
------------------------------------------------------------------------
}}}
The test is then considered as successful in the final output.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2113>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2077: include RNSID in ET
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: Hydro_RNSID |
-----------------------------------+----------------------------------------
Pull request is here:
https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/3
/new-initial-data-thorn-for-grhydro/diff
It generate ID for rotating star either with uniform rotational
profile or describe by differentialy rotating j-law.
testsuite par file provided and tested
example of usage parfile in par subdirectory as perl script that
generate par file with resolution dx=0.75 suited for workstation tests.
Hydro_RNSID/par/speed.rpar generate par file usefull to peform
speed test
two stand alone utility are generate at compile time to [RNS]
generate initial models (to be imported in Cactus) amd to read [RNS_read]
the generated initial model
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2077>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit