python tests don't work when code coverage flags are used?

[edwardhartnett]

When I run the code coverage flags with python on, then the python tests fail. They should not.

Are the python tests doing something goofy like looking at text output?

[jbathegit]

I think this may be a systemic issue that depends on more than just whether or not code coverage flags are used. I don't normally run with those flags, because I do most of my work on the WCOSS using the Intel compilers, and in fact I don't even normally test with Python enabled. But I did try testing this library using -DENABLE_PYTHON=ON yesterday on the WCOSS, after manually loading in the python/3.6.3 module. Everything compiled OK, but all of the python tests still failed during the ctest check, even though I'm not using code coverage flags.

I think we may need @aerorahul to take a look at this when he has some time.

[aerorahul]

It is likely that when `creating the python API, the code coverage flags need to be included, and are likely not.
I am not sure I will get to this anytime soon.