• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • junit-plugin
    • None
    • Platform: All, OS: All

      http://deadlock.netbeans.org/hudson/job/NB-Core-Build/1909/testReport/org.netbeans.modules.masterfs.filebasedfs/BaseFileObjectTestHid/testFileUtilToFileObjectIsValid/

      shows

      "Standard Error

      Skipping org.openide.filesystems.FileObjectTestHid.testWriteReadExclusion
      Skipping org.openide.filesystems.FileObjectTestHid.testWriteReadExclusionDeadlock"

      but this information, from SuiteResult, is not available in the corresponding
      /api/xml.

      I guess the problem is that what is exposed is a hierarchy of TestResult ->
      PackageResult -> ClassResult -> CaseResult. The SuiteResult's most commonly
      correspond to ClassResult's but this is not always true, and we would not want
      to serialize a SuiteResult's info inside a CaseResult's output since this would
      often create duplicate output.

      Could perhaps have the root TestResult also enumerate SuiteResult's as a
      separate subtree, with the serialized information being the name, duration,
      timestamp, stdout/err, and perhaps list of CaseResult names for cross-linking?
      Of course these names are not guaranteed to be unique. Ideally, the XML
      structure would expose the CaseResult.parent -> SuiteResult links using e.g.
      generated element IDs, but this may be beyond the capabilities of your XML
      serialization framework.

          [JENKINS-2760] No stdout/stderr in XML API

          Despite the possible performance problem, I think the easiest thing to do is to
          expose stdout/err from CaseResult.

          We might also want the URL that returns the raw JUnit XML that Hudson saves in
          its file system. That is likely just as parse-able and have no duplication problems.

          Kohsuke Kawaguchi added a comment - Despite the possible performance problem, I think the easiest thing to do is to expose stdout/err from CaseResult. We might also want the URL that returns the raw JUnit XML that Hudson saves in its file system. That is likely just as parse-able and have no duplication problems.

          Code changed in hudson
          User: : kohsuke
          Path:
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=14347
          Log:
          [FIXED JENKINS-2760] Recording this change that was made in 1.272

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : kohsuke Path: trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=14347 Log: [FIXED JENKINS-2760] Recording this change that was made in 1.272

          Jesse Glick added a comment -

          Fix did not work and in fact regressed more important things; see issue #2839.

          Jesse Glick added a comment - Fix did not work and in fact regressed more important things; see issue #2839.

          Jesse Glick added a comment -
              • Issue 2839 has been marked as a duplicate of this issue. ***

          Jesse Glick added a comment - Issue 2839 has been marked as a duplicate of this issue. ***

          Jesse Glick added a comment -

          I think I have a fix.

          Jesse Glick added a comment - I think I have a fix.

          Code changed in hudson
          User: : jglick
          Path:
          trunk/hudson/main/core/src/main/java/hudson/tasks/junit/CaseResult.java
          trunk/hudson/main/core/src/main/java/hudson/tasks/junit/SuiteResult.java
          trunk/hudson/main/core/src/main/java/hudson/tasks/junit/TestResult.java
          http://fisheye4.cenqua.com/changelog/hudson/?cs=15045
          Log:
          [FIXED JENKINS-2760] Rearranging /testReport/api/xml to be more like junitResult.xml.
          Now groups results into suites, then cases.
          A suite has a name, which is usually - but not always - identical to the class name of its cases.
          (If you have static Test suite() methods, then it could be different.)
          stdout/stderr is associated with a suite. (JUnit does not record which case produced stdio.)
          Also exporting failedSince and skipped attrs.
          junitResult.xml is similar, but does not represent FAILED vs. REGRESSION or age (does have failedSince).
          Prior fixes failed to export stdout/stderr, and in fact made case details invisible.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : jglick Path: trunk/hudson/main/core/src/main/java/hudson/tasks/junit/CaseResult.java trunk/hudson/main/core/src/main/java/hudson/tasks/junit/SuiteResult.java trunk/hudson/main/core/src/main/java/hudson/tasks/junit/TestResult.java http://fisheye4.cenqua.com/changelog/hudson/?cs=15045 Log: [FIXED JENKINS-2760] Rearranging /testReport/api/xml to be more like junitResult.xml. Now groups results into suites, then cases. A suite has a name, which is usually - but not always - identical to the class name of its cases. (If you have static Test suite() methods, then it could be different.) stdout/stderr is associated with a suite. (JUnit does not record which case produced stdio.) Also exporting failedSince and skipped attrs. junitResult.xml is similar, but does not represent FAILED vs. REGRESSION or age (does have failedSince). Prior fixes failed to export stdout/stderr, and in fact made case details invisible.

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: