Issue942 durack1 python279 update

[durack1]

@doutriaux1 @aashish24 let's see if this passes the travis test and merge it as a 2.2 milestone

[durack1]

@aashish24 it seems that the linux build just fell over for no reason again, the OS X build seems to have completed without a problem.. This is where it seems to have hung:

[ 18%] Completed 'libXSLT'
[ 18%] Built target libXSLT
Scanning dependencies of target zlib
[ 18%] Creating directories for 'zlib'
[ 19%] Performing download step (download, verify and extract) for 'zlib'
-- downloading...
src='http://uv-cdat.llnl.gov/cdat/resources/zlib-1.2.5.tar.gz'
dst='/home/travis/build/UV-CDAT/_build/zlib-1.2.5.tar.gz'
timeout='none'
attempt 1
-- [download 0% complete]
-- [download 1% complete]
...
-- [download 99% complete]
-- [download 100% complete]
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated

I'll tweak the PR and send it through again..

[durack1]

@aashish24 @dlonie it seems like this linux build is really unstable as it's failed again (second time around the OS X passed fine, again):

The command "cd _build" exited with 0.
0.02s$ cmake -DGIT_PROTOCOL=git:// -DCDAT_BUILD_MODE=LEAN -DCDAT_BUILD_GRAPHICS=ON -DCDAT_BUILD_SCIPY=OFF ../uvcdat
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
CMake 2.8.8 or higher is required. You are running version 2.8.7
-- Configuring incomplete, errors occurred!
The command "cmake -DGIT_PROTOCOL=git:// -DCDAT_BUILD_MODE=LEAN -DCDAT_BUILD_GRAPHICS=ON -DCDAT_BUILD_SCIPY=OFF ../uvcdat" exited with 1.
...
Error in read script: /home/travis/build/UV-CDAT/uvcdat/CMake/travis_build.cmake
The command "ctest -VV -S ../uvcdat/CMake/travis_build.cmake" exited with 255.

[alliepiper]

It's not a build stability issue, they're using an out of date cmake on that machine (fourth line down).

[durack1]

@dlonie is there a way to force an updated cmake build in the travis build test? It seems to me that 3 times out of 4 the test failing just due to bad configuration is something which renders the service almost useless..

[alliepiper]

I agree, but I'm not sure how much control we have over that. @aashish24 might know more?

[doutriaux1]

@dlonie we could build cmake if/when we detect an older version. I do this for pcmdi_metrics.git

[doutriaux1]

works for me and ctests pass on my ubunutu merging