You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by do...@apache.org on 2011/07/22 13:24:06 UTC

svn commit: r1149568 - /buildr/trunk/spec/java/bdd_spec.rb

Author: donaldp
Date: Fri Jul 22 11:24:05 2011
New Revision: 1149568

URL: http://svn.apache.org/viewvc?rev=1149568&view=rev
Log:
Fix spelling and grammar in the comment

Modified:
    buildr/trunk/spec/java/bdd_spec.rb

Modified: buildr/trunk/spec/java/bdd_spec.rb
URL: http://svn.apache.org/viewvc/buildr/trunk/spec/java/bdd_spec.rb?rev=1149568&r1=1149567&r2=1149568&view=diff
==============================================================================
--- buildr/trunk/spec/java/bdd_spec.rb (original)
+++ buildr/trunk/spec/java/bdd_spec.rb Fri Jul 22 11:24:05 2011
@@ -28,9 +28,9 @@ describe Buildr::RSpec do
   end
 
   it 'should read passed specs from result yaml' do
-    # This test fails on the CI machine if the spec is run as part of a suite but not if ru individually
-    # This seems to indicate that there is interaction with some other test but until that is identified
-    # the test has been marked as pending on the ci box
+    # This test fails on the CI machine if the spec is run as part of a suite but not if run individually
+    # This seems to indicate that there is interaction with some other test but until that other test is
+    # identified the test has been marked as pending on the ci box
     pending "Unable to determine why it fails on the CI machine so disabling" if `hostname` == "vesta.apache.org"
     write('src/spec/ruby/success_spec.rb', 'describe("success") { it("is true") { nil.should be_nil } }')
 
@@ -39,9 +39,9 @@ describe Buildr::RSpec do
   end
 
   it 'should read result yaml to obtain the list of failed specs' do
-    # This test fails on the CI machine if the spec is run as part of a suite but not if ru individually
-    # This seems to indicate that there is interaction with some other test but until that is identified
-    # the test has been marked as pending on the ci box
+    # This test fails on the CI machine if the spec is run as part of a suite but not if run individually
+    # This seems to indicate that there is interaction with some other test but until that other test is
+    # identified the test has been marked as pending on the ci box
     pending "Unable to determine why it fails on the CI machine so disabling" if `hostname` == "vesta.apache.org"
     success = File.expand_path('src/spec/ruby/success_spec.rb')
     write(success, 'describe("success") { it("is true") { nil.should be_nil } }')