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

Test failures not appearing in test trend chart

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      For a build we are running, the test failures don't show up in the test trend
      chart. There is no entry for any failed build. I suppose that makes sense for
      some failures, but when the only failure I can see is with test results, it
      seems like it should appear. (This seems flagrant, so I wonder if I'm just doing
      something wrong.)

      This is a build for a Maven project, but it's set up manually rather than using
      the Maven integration (which didn't seem to actually do anything - but I haven't
      paid close enough attention to know how to write up a report on that).

        Attachments

          Activity

          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          This is because Maven reports a non-0 exit code upon a failed test, causing
          Hudson to believe that the build failed in more fatal way (as a result, you'll
          also see red, instead of yellow status color.)

          Hudson should be able to at least collect tests, though. So I'll see if I can
          make that change.

          The maven integration is still a work in progress, but it should do the basic
          stuff already — if you see something strange or unintuitive, it would be great
          if you could file those as issues, too.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - This is because Maven reports a non-0 exit code upon a failed test, causing Hudson to believe that the build failed in more fatal way (as a result, you'll also see red, instead of yellow status color.) Hudson should be able to at least collect tests, though. So I'll see if I can make that change. The maven integration is still a work in progress, but it should do the basic stuff already — if you see something strange or unintuitive, it would be great if you could file those as issues, too.
          Hide
          tompalmer tompalmer added a comment -

          Sounds like a good idea for collecting tests even if there's a failure code (at
          least for Maven? - maybe in general?). If any results are found at all, you
          could just include them. Otherwise, don't plot it (or let it show 0? - pros and
          cons). Some variation on that theme would work for most cases, I think,

          Show
          tompalmer tompalmer added a comment - Sounds like a good idea for collecting tests even if there's a failure code (at least for Maven? - maybe in general?). If any results are found at all, you could just include them. Otherwise, don't plot it (or let it show 0? - pros and cons). Some variation on that theme would work for most cases, I think,
          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          Fixed in 1.105.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - Fixed in 1.105.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            tompalmer tompalmer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: