New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ctest 'fails' if python has not been run interactively at least once (anonymous logging problem) #456

Closed
jypeter opened this Issue Apr 22, 2014 · 5 comments

Comments

Projects
None yet
4 participants
@jypeter

jypeter commented Apr 22, 2014

If python has not been run interactively at least once (with some modules from PCMDI imported?), there is no anonymouslog file

~/.uvcdat/.anonymouslog

and running ctest in the build directory ends up with all tests failing (except CDMS_Test_09)

54/71 Test #54: CDMS_Test_08 .......................***Failed    0.12 sec
      Start 55: CDMS_Test_09
55/71 Test #55: CDMS_Test_09 .......................   Passed    0.11 sec
      Start 56: CDMS_Test_10
56/71 Test #56: CDMS_Test_10 .......................***Failed    0.55 sec
[...]
71/71 Test #71: CDMS_Test_pack .....................***Failed    0.12 sec

1% tests passed, 70 tests failed out of 71

Total Test time (real) =  18.17 sec

The following tests FAILED:
      1 - run_uvcdat (Failed)
      2 - cdms_test (Failed)

I'm not sure when the file is created. I have had to import several modules before I was prompted about the anonymous logging

>>> import re
>>> import cdtime
>>> import numpy
>>> import genutil
Allow anonymous logging usage to help improve UV-CDAT? (you can also set the environment variable UVCDAT_ANONYMOUS_LOG to yes or     no) [yes/no]no
>>> 

What do you do with the anonymous logging? How do you send the results to PCMDI? Is there a chance that this may induce some lag when using uv-cdat based scripts? Logging seems like a tempting idea that could have unforeseen side-effects

@jypeter jypeter changed the title from ctest 'fails' if python has not been run interactively at least once to ctest 'fails' if python has not been run interactively at least once (anonymous logging problem) Apr 22, 2014

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Apr 22, 2014

@aashish24 I know we set the UVCDAT_ANONYMOUS_LOG env variable in CMakeLists.txt, is it not picked up by ctest?

@aashish24

This comment has been minimized.

Contributor

aashish24 commented Apr 26, 2014

No it won't because that is setup during the build time. We can setup environment for crest like this:

SET (CTEST_ENVIRONMENT
"DISPLAY=:0"
"GLIBCPP_FORCE_NEW=1"
"CC=gcc-3.4"
"CXX=g++-3.4"
)

do you want to push a branch for this?

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 17, 2014

@aashish24 we should implement this, and while at it set the env correctly so that we don't need to source setup_runtime

@doutriaux1 doutriaux1 added the Build label Oct 17, 2014

@doutriaux1 doutriaux1 added this to the 2.1 milestone Oct 17, 2014

@doutriaux1 doutriaux1 modified the milestones: 2.1, 2.2 Feb 2, 2015

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Feb 21, 2015

@aashish24 we should add this for 2.2

@aashish24

This comment has been minimized.

Contributor

aashish24 commented Feb 21, 2015

yes.. this is problemetic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment