5

I've added a patch for the rules module. The patch detail page says the test status is postponed.

What does that exactly mean? Is there anything I should do to get the patch tested?

7

The problem is that the current Rules branch is currently failing an already commited test. While this should obviously not be possible, as tests should be green before they are commited, rare circumstances will cause this to happen from time to time.

Since an already existing test does fail, we know that testing with your new patch will also fail, whether your patch is correct or not. Thus all tests are postponed until the existing and breaking test is fixed.

4

To add to what Letharion said, these are the Rules 7.x-2.x tests that fail.

screenshot

The branch tests are the tests included in the module. To see the test ran for a module branch, you can check this page; the modules are ordered alphabetically, and by their version.

screenshot

As the project tests are already failing, it doesn't make sense to test the patch; they would fail even when the patch would be correct.

The purpose of the project tests is exactly to verify that changes in the code don't introduce errors. They can be run after a commit, or before a patch is committed.

  • 1
    I think this question should be marked under faq, because it is useful information which most of us didn't know before. – AjitS Jul 6 '12 at 13:22
  • If we did that with everything "most didn't know", the faq would become rather long. :) – Letharion Jul 6 '12 at 13:28
  • @Letharion : yes, that makes sense to me :) – AjitS Jul 6 '12 at 13:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.