jUnit discarding <testsuite> tags when certain attributes are equal

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Critical
    • Component/s: junit-plugin, xunit-plugin
    • Environment:

      The cause of this problem appears to be the `name` and `timestamp` attributes of a `<testsuite>` tag being equal. When processing the report file, if a `<testsuite>` tag is encountered where these attributes are the same as one that was already seen, the new tag is silently ignored.

      This happens with the jUnit publisher and xUnit. It even happens if only the timestamps are equal, which is a nasty bug since timestamps shouldn't be used to uniquely identify a testsuite when they have different names. It looks like Jenkins publishes the first suite and ignores any other XML files with the same timestamp. If the timestamps are empty, they are all reported. Reproduced with Jenkins 1.595 with junit 1.2-beta4, and also reproduced with the latest Jenkins 1.627 and junit 1.8.

      See the two attached test_result_*.xml to reproduce: Archive them via junit and only testFoo is reported. If you change the timestamp attribute of either, they both are reported.

        1. build-123-input.xml
          48 kB
        2. build-123-result.xml
          102 kB
        3. build-124-input.xml
          48 kB
        4. build-124-result.xml
          109 kB
        5. test_result_1012678300206172099.xml
          0.3 kB
        6. test_result_9114558122204227176.xml
          0.3 kB

            Assignee:
            Unassigned
            Reporter:
            Kris Reeves
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: