-
Notifications
You must be signed in to change notification settings - Fork 53
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
release version different from internal version; circleci tests failing because nipype printing out a message #185
Comments
Okay -- just added a github v1.3.7 release: https://github.com/nipy/mindboggle/releases/tag/v1.3.7 Does that take care of things? |
that should help. there is an error that is cropping up in doctests because nipype is printing out a message. this could be avoided by importing nipype earlier. but i have to think if this is indeed a change we want to make in how nipype reports the version change. |
When do you suggest I import nipype, or should I wait for your change in nipype? |
@satra -- Why would I get a doctest error when the command in question is returning something (area_file)?
|
@satra -- I moved nipype installation to earlier in the conda install line of neurodocker.sh, but circleci tests are still failing:
|
this is because the first time nipype is imported in a terminal interaction setting, it will try to check if you are running the latest version. this results in a stdout which you are seeing. one way to avoid the issue is to add another dummy line after that doctest. we will have to figure out how best to change nipype behavior, but for now we are keeping this. |
By "dummy line after that doctest", do you mean an empty line ">>> " after the line: |
@binarybottle - your release versions (see github releases for mindboggle) are different from internal versions. so etelemetry is getting misleading info from the source code and github.
where as internally it says: 1.3.6/7 now
The text was updated successfully, but these errors were encountered: