Browse files

[rake] reorder rake args so --trace is at the end

It looks like Rake changed and now --trace takes options and blows up if
it's ahead of the rake target. I didn't look very deeply into it; moving
--trace to the end of the command makes everything work again.
  • Loading branch information...
1 parent 39991b0 commit 3a66324b70728630cb53a72d6c268ea084ab9dee Al Tobey committed Nov 13, 2012
@@ -91,10 +91,10 @@ build_hastur () {
# bundle / rake are placed in the path with update-alternatives in the root setup
# see
- $personality chroot $path bash -c "cd /tmp/hastur-server && rake --trace build"
+ $personality chroot $path bash -c "cd /tmp/hastur-server && rake build --trace"
$personality chroot $path bash -c "cd /tmp/hastur-server && bundle install" # could fail, don't care
- $personality chroot $path bash -c "cd /tmp/hastur-server && rake --trace $target"
- require $personality chroot $path bash -c "cd /tmp/hastur-server && rake --trace $target"
+ $personality chroot $path bash -c "cd /tmp/hastur-server && rake $target --trace"
+ require $personality chroot $path bash -c "cd /tmp/hastur-server && rake $target --trace"
for arch in amd64 i386
@@ -37,4 +37,4 @@ echo "
-COVERAGE=true bundle exec rake --trace test:integrations
+COVERAGE=true bundle exec rake test:integrations --trace
@@ -9,4 +9,4 @@ gem uninstall bundler -v 1.1.1
gem install --no-rdoc --no-ri bundler -v 1.1.0
bundle update # Update to latest versions since this is a gem
#bundle install
-COVERAGE=true bundle exec rake --trace test:units:full
+COVERAGE=true bundle exec rake test:units:full --trace

0 comments on commit 3a66324

Please sign in to comment.