#2114: Carpet/Carpet/test/64k2.par test fails on Jenkins test machine
Reporter:Ian Hinder
Status:open
Milestone:
Version:development version
Type:bug
Priority:minor
Component:Carpet

Changes (by Roland Haas):

status:open (was new)

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.

Keyword:

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2114/carpet-carpet-test-64k2par-test-fails-on