Skip to content
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

out/err output of rosdoc jobs is separated #9

Open
dirk-thomas opened this issue Dec 6, 2012 · 1 comment
Open

out/err output of rosdoc jobs is separated #9

dirk-thomas opened this issue Dec 6, 2012 · 1 comment
Labels

Comments

@dirk-thomas
Copy link
Member

Looking at http://jenkins.willowgarage.com:8080/job/doc-groovy-control/26/console it looks like stdout is printed first and afterwards comes stderr. That makes reading the log extremely difficult. The order of output should be preserved.

-- Check for working C compiler: /usr/lib/ccache/gcc
-- Check for working C compiler: /usr/lib/ccache/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/lib/ccache/c++
-- Check for working CXX compiler: /usr/lib/ccache/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Using CATKIN_DEVEL_PREFIX: /home/rosbuild/hudson/workspace/doc-groovy-control/doc_stacks/2012-12-05_23-48-17.025681/build_repo/devel
-- Using CMAKE_PREFIX_PATH: /opt/ros/groovy
-- This workspace overlays: /opt/ros/groovy
-- Found PythonInterp: /usr/bin/python (found version "2.7.3")
-- Looking for include files CMAKE_HAVE_PTHREAD_H
-- Looking for include files CMAKE_HAVE_PTHREAD_H - found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE 
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- catkin 0.5.52
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing packages in topological order:
-- ~~  - control_msgs
-- ~~  - control
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ add_subdirectory(control_msgs/control_msgs)
-- control_msgs: 1 messages, 0 services
-- +++ add_subdirectory(control_msgs/compatibility/control)
-- Configuring incomplete, errors occurred!

control_msgs has BUILD message dependencies:
  -std_msgs
  -trajectory_msgs
  -geometry_msgs
  -actionlib_msgs
control_msgs has BUILD dependencies:
  -catkin
  -genmsg
  -langs-dev
  -std_msgs
  -trajectory_msgs
  -geometry_msgs
  -actionlib_msgs
catkingenmsglangs-devstd_msgstrajectory_msgsgeometry_msgsactionlib_msgs
  Export my include dir: 
  Export my lib dir: 
CMake Error at /opt/ros/groovy/share/catkin/cmake/catkin_workspace.cmake:53 (add_subdirectory):
  The source directory

/home/rosbuild/hudson/workspace/doc-groovy-control/doc_stacks/2012-12-05_23-48-17.025681/control_msgs/compatibility/control


  does not contain a CMakeLists.txt file.
Call Stack (most recent call first):
  CMakeLists.txt:51 (catkin_workspace)

/!\  Failed to execute command '['cmake', '..']'
FAILED TO CALL CMAKE ON CATKIN REPOS```
@eitanme
Copy link
Contributor

eitanme commented Dec 19, 2012

I'm not exactly sure what you're saying here. What, specifically, would you expect to be in a different order? The following snippet around the error looks OK to me:

  Export my lib dir: 
CMake Error at /opt/ros/groovy/share/catkin/cmake/catkin_workspace.cmake:53 (add_subdirectory):
  The source directory

    /home/rosbuild/hudson/workspace/doc-groovy-control/doc_stacks/2012-12-05_23-48-17.025681/control_msgs/compatibility/control

  does not contain a CMakeLists.txt file.
Call Stack (most recent call first):
  CMakeLists.txt:51 (catkin_workspace)



/!\  Failed to execute command '['cmake', '..']'
FAILED TO CALL CMAKE ON CATKIN REPOS
There will be no messages in documentation and some python docs may fail

Once I know what's flipped I can try to look into things, but I believe they're printing out in the correct order.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants