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

Gazebo Tests Delete Workspace Every Run (ros ticket #3793) #88

Open
ahendrix opened this issue Sep 9, 2013 · 1 comment
Open

Gazebo Tests Delete Workspace Every Run (ros ticket #3793) #88

ahendrix opened this issue Sep 9, 2013 · 1 comment

Comments

@ahendrix
Copy link
Member

ahendrix commented Sep 9, 2013

For some strange and annoying reason, hudson deletes its workspace every time it builds the test.

{{{
At revision 27633
Fetching 'https://code.ros.org/svn/ros-pkg/stacks/sound_drivers/tags/latest' at -1 into '/home/wgsim/hudson/workspace/gazebo-milestone-tests/ros-pkg/sound_drivers'
At revision 27633
Fetching 'https://code.ros.org/svn/ros-pkg/stacks/imu_drivers/tags/latest' at -1 into '/home/wgsim/hudson/workspace/gazebo-milestone-tests/ros-pkg/imu_drivers'
At revision 27633
At revision 27633
Updating https://code.ros.org/svn/wg-ros-pkg/trunk
svn: Failed to add directory 'stacks/executive_trex/trex': an unversioned directory of the same name already exists
Updated failed due to local files. Getting a fresh workspace
Checking out https://code.ros.org/svn/ros/stacks/ros/tags/rc
A test
A test/test_roswtf
A test/test_roswtf/test

}}}

trac data:

@ahendrix
Copy link
Member Author

ahendrix commented Sep 9, 2013

[gerkey] I don't see any reason for it do that. I manually deleted the entire workspace and kicked off another build (http://build.willowgarage.com/job/gazebo-milestone-tests/4068/). Perhaps there was something stale in the file system that was preventing Hudson from truly wiping out the workspace. We'll see what happens on the build after this one.

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

No branches or pull requests

1 participant