Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-4378

Maven2 test failures not resulting in build failure, or build unstable.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • maven-plugin
    • None
    • Platform: Macintosh, OS: Mac OS X

      I have a Maven2 project in Hudson using the Maven2 project type.

      When the project builds, there is a unit test that fails (SureFire), but the
      project build is not marked as unstable, nor does it fail.

      If I set the "maven.test.failure.ignore=false" property, the project build will
      fail, but the failed test result is not shown.

      I ran hudson manually in the terminal, but did not see any errors.

          [JENKINS-4378] Maven2 test failures not resulting in build failure, or build unstable.

          elberry created issue -

          Andrew Bayer added a comment -

          This is a multi-module project, yes? Can you drill down to the module with test
          failures and see if it's marked as unstable?

          Andrew Bayer added a comment - This is a multi-module project, yes? Can you drill down to the module with test failures and see if it's marked as unstable?

          elberry added a comment -

          That's correct, it's a multi-module project, and no, if I drill down the modules
          in Hudson, they all show they passed successfully. None of the modules show that
          the tests failed, and are marked with the yellow ball.

          elberry added a comment - That's correct, it's a multi-module project, and no, if I drill down the modules in Hudson, they all show they passed successfully. None of the modules show that the tests failed, and are marked with the yellow ball.

          Alan Harder added a comment -

          Are you still able to see this problem in a recent Hudson release?
          If you can attach a simple pom+src bundle we can use to reproduce the problem it would help, thanks.

          Alan Harder added a comment - Are you still able to see this problem in a recent Hudson release? If you can attach a simple pom+src bundle we can use to reproduce the problem it would help, thanks.

          Alan Harder added a comment -

          Reopen if you still see this issue on a recent Hudson release, thanks.

          Alan Harder added a comment - Reopen if you still see this issue on a recent Hudson release, thanks.
          Alan Harder made changes -
          Resolution New: Postponed [ 6 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          flottis added a comment -

          Hi,

          We are experiencing the exact same problems as mentioned above. I just installed the latest stable release (1.386) but faild junit tests does not mark the project as unstable. Some project setup facts:

          • Maven2
          • JUnit
          • Surefire
          • Multi-module

          Let me know if you need src+pom to reproduce this and I'll throw something together.

          flottis added a comment - Hi, We are experiencing the exact same problems as mentioned above. I just installed the latest stable release (1.386) but faild junit tests does not mark the project as unstable. Some project setup facts: Maven2 JUnit Surefire Multi-module Let me know if you need src+pom to reproduce this and I'll throw something together.
          flottis made changes -
          Resolution Original: Postponed [ 6 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          flottis made changes -
          Link New: This issue is duplicated by JENKINS-6700 [ JENKINS-6700 ]

            Unassigned Unassigned
            elberry elberry
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: