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

Release 1.30 all test results are duplicated

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: junit-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.252
      Junit-plugin 1.30
      Parallel Test Executor 1.13
    • Similar Issues:

      Description

      Since version 1.30 (1.29 still works), all my tests are reported twice, duplicating all test results.
      Probably caused by fix JENKINS-48583.

      Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

      Configured publish report 'fileset includes': */report/test/TEST-.xml

      I'm using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes. Running the tests without this plugin (so not in parallel), the report is ok (no duplicates).

      If more information is required please let me know.

        Attachments

          Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-48583 Junit test reports are dropped if they have a timestamp within the same second as another test report

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

            Activity

            Ascending order - Click to sort in descending order
            ricktw Rick Oosterholt created issue -
            ricktw Rick Oosterholt made changes -
            Field Original Value New Value
            Link This issue is caused by JENKINS-48583 [ JENKINS-48583 ]
            ricktw Rick Oosterholt made changes -
            Description Since version 1.30, all my tests are reported twice, duplicating all test results.
            Probably caused by fix JENKINS-48583.

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.             		Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.
            ricktw Rick Oosterholt made changes -
            Description Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.             		Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.
            ricktw Rick Oosterholt made changes -
            Description Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.             		Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            Configured publish report 'fileset includes': **/report/test/TEST-*.xml

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.
            ricktw Rick Oosterholt made changes -
            Description Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            Configured publish report 'fileset includes': **/report/test/TEST-*.xml

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.             		Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            Configured publish report 'fileset includes': \*\*/report/test/TEST-\*.xml

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.
            wpballard William Ballard made changes -
            Comment [ Still seeing this issue. I know the "is caused by" is showing as resolved, but we are still seeing it in our environments.  ]
            ricktw Rick Oosterholt made changes -
            Description Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            Configured publish report 'fileset includes': \*\*/report/test/TEST-\*.xml

            I'm also using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes.

            If more information is required please let me know.             		Since version 1.30 {color:#c1c7d0}_(1.29 still works)_{color}, all my tests are reported twice, duplicating all test results.
             Probably caused by fix JENKINS-48583.

            Each suite is reported once, all tests inside it are reported twice (once with the original name and once appended with '_2'; e.g. my.package.name.suite.testCaseOne and my.package.name.suite.testCaseOne_2).

            Configured publish report 'fileset includes': **/report/test/TEST-*.xml

            I'm using the Parallel Test Executor plugin to run all my tests in parallel in 6 jobs running on different nodes. Running the tests without this plugin (so not in parallel), the report is ok (no duplicates).

            If more information is required please let me know.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ricktw Rick Oosterholt
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: