Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8153628

tmtools/jstack/stacktrace tests should not print full stacktraces to stdout/stderr

    Details

    • Subcomponent:
      svc

      Description

      Debuggee processes in tmtools/jstack/stacktrace could generate extremely deep call stacks.
      When test failed, stacktraces obtained via jstack and via Thread.getAllStackTraces dumped to stdout.
      Also, if failure occurred due to mismatches in stack traces, then all mismatches dumped to stdout as well.

      Such verbosity leads to huge log files, that are very difficult to analyze and could not be parsed by aurora.
      Latter cause many unmatched failures.

      See example: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=419505.7u60_VM_promotion-524#vm.tmtools%20%28dtonga%29_tmtools/jstack/stacktrace_complex_scenario/complex_scenario

      It would be nice if such tests dump stacktraces to different log files and put only failure reason to stdout/stderr.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              fzhinkin Filipp Zhinkin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: