Unit tests don't run right anymore now that we implicitly depend on grizzly 1.7.6. We should probably make the unit tests run using something like tox, to hide the environment needed so that we don't need the host system that runs the tests to change much.
REVIEW: http://review.gluster.org/4781 (object-storage: use tox for unit tests; fix em too) posted (#1) for review on master by Peter Portante (pportant)
REVIEW: http://review.gluster.org/4781 (object-storage: use tox for unit tests; fix em too) posted (#2) for review on master by Peter Portante (pportant)
COMMIT: http://review.gluster.org/4781 committed in master by Anand Avati (avati) ------ commit 6a7d28c0f8c107baf376eceb9fc05d9e80bf74e5 Author: Peter Portante <peter.portante> Date: Thu Apr 4 13:08:32 2013 -0400 object-storage: use tox for unit tests; fix em too Add the ability to use tox for unit tests, since it helps us solve the problem of supporting multiple branches that require different versions of dependencies, and allows us to possibly support multiple versions of python in the future. Also fix the code to work with pre-grizzly environments, by not requiring the constraints backport. Also fixed the xattr support to work with both pyxattr and xattr modules. And fixed the ring tests to also work without a live /etc/swift directory. BUG: 948657 (https://bugzilla.redhat.com/show_bug.cgi?id=948657) Change-Id: I2be79c8ef8916bb6552ef957094f9186a963a068 Signed-off-by: Peter Portante <peter.portante> Reviewed-on: http://review.gluster.org/4781 Reviewed-by: Alex Wheeler <wheelear> Tested-by: Alex Wheeler <wheelear> Reviewed-by: Anand Avati <avati>
REVIEW: http://review.gluster.org/4947 (object-storage: use tox for unit tests; fix em too) posted (#1) for review on release-3.4 by Alex Wheeler (wheelear)