Failing test

[matham]

After fixing #1 we still ran into the following test failure.

cd tests/ && python -m unittest
......................../home/ayon/.virtualenvs/myriad_ayon/lib/python3.4/tempfile.py:699: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/TimeseriesObji17e0p2i'>
  _warnings.warn(warn_message, ResourceWarning)
./home/ayon/.virtualenvs/myriad_ayon/lib/python3.4/tempfile.py:699: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/VarOnlyObjRenderpp6wxj2b'>
  _warnings.warn(warn_message, ResourceWarning)
./home/ayon/.virtualenvs/myriad_ayon/lib/python3.4/tempfile.py:699: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/RenderObjacbxgaw4'>
  _warnings.warn(warn_message, ResourceWarning)
.make[1]: Entering directory '/tmp/tmp8c8ksfi1'
gcc -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -x c -Wall -Wextra -Wpedantic -Wno-unused-parameter -Wno-unknown-pragmas -std=gnu99 -fopenmp -Og -g3 -fsanitize=undefined -I. -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -o Compartment.o -c Compartment.cu
gcc -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -x c -Wall -Wextra -Wpedantic -Wno-unused-parameter -Wno-unknown-pragmas -std=gnu99 -fopenmp -Og -g3 -fsanitize=undefined -I. -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -o Mechanism.o -c Mechanism.cu
gcc -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -x c -Wall -Wextra -Wpedantic -Wno-unused-parameter -Wno-unknown-pragmas -std=gnu99 -fopenmp -Og -g3 -fsanitize=undefined -I. -DFAST_EXP -DNUM_THREADS=1 -DDEBUG -o MyriadObject.o -c MyriadObject.cu
MyriadObject.cu:12:25: fatal error: RenderObj.cuh: No such file or directory
compilation terminated.
Makefile:60: recipe for target 'MyriadObject.o' failed
make[1]: *** [MyriadObject.o] Error 1
make[1]: Leaving directory '/tmp/tmp8c8ksfi1'
E/home/ayon/.virtualenvs/myriad_ayon/lib/python3.4/tempfile.py:699: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/tmp8c8ksfi1'>
  _warnings.warn(warn_message, ResourceWarning)


================================================================================
Log for Error @ <test_myriad_simul.TestMyriadSimulObject testMethod=test_simul_run> 
--------------------------------------------------------------------------------
�[40m�[37mmyriad.myriad_simul - DEBUG - <class 'myriad.myriad_object.MyriadObject'>module imported�[0m
�[40m�[37mmyriad.myriad_simul - DEBUG - <class 'myriad.myriad_compartment.Compartment'>module imported�[0m
�[40m�[37mmyriad.myriad_simul - DEBUG - <class 'myriad.myriad_mechanism.Mechanism'>module imported�[0m

Traceback (most recent call last):
  File "/home/ayon/myriad/tests/test_myriad_simul.py", line 54, in test_simul_run
    comm = obj.run()
  File "/home/ayon/myriad/myriad/myriad_simul.py", line 368, in run
    ["make", "-C", template_dir.name, "-j1", "all"])
  File "/usr/local/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', '-C', '/tmp/tmp8c8ksfi1', '-j1', 'all']' returned non-zero exit status 2
================================================================================

.................................
======================================================================
ERROR: test_simul_run (test_myriad_simul.TestMyriadSimulObject)
Tests running a simulation object
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ayon/myriad/tests/test_myriad_simul.py", line 54, in test_simul_run
    comm = obj.run()
  File "/home/ayon/myriad/myriad/myriad_simul.py", line 368, in run
    ["make", "-C", template_dir.name, "-j1", "all"])
  File "/usr/local/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', '-C', '/tmp/tmp8c8ksfi1', '-j1', 'all']' returned non-zero exit status 2

----------------------------------------------------------------------
Ran 61 tests in 1.097s

FAILED (errors=1)
Makefile:7: recipe for target 'test' failed
make: *** [test] Error 1

I suspect it's because there's some global storage of all the created objects which get rendered (later?), even if we didn't ask explicitly. And this somehow clashes with the template that was intended to be rendered. Or something like that. For example, if we force rendering these test objects after they are created (unlike currently where they are just abandoned) into their own folder this issue doesn't seem to occur. Of course force rendering is not a a proper solution.

So perhaps there's a way to remove those un-rendered objects from being accidentally rendered (assuming that's the issue).