Make sure you have read:
Then, follow these steps to fix a failing spec:
git checkout -b branch_nameto create a new branch (where branch_name is a brief description for the problem you are fixing.)
raketo ensure that all CI specs are passing.
bin/mspec spec/some/spec_file.rbto confirm the spec fails.
rake buildto build your change.
bin/mspec spec/some/spec_file.rbto see if your change makes the spec pass.
raketo ensure there are no regressions.
git status, git add, git commit, etc. Any changes made to the spec files under the spec/ruby directory must be in a different commit from changes made to other Rubinius source code files.
When your pull request is accepted by the Rubinius project, you’ll get a commit bit for the Rubinius repository. Let Evan, Brian or Dirkjan know what your Github username is.