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

Excluding compile messages should only be printed with PrintCompilation

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P3 P3
    • 9
    • 9
    • hotspot
    • None
    • b92

        With JDK-8046155 we now print "Excluding compile" messages for each excluded compilation. Many tests specify "-XX:CompileCommand=compileonly, ..." which results in dozens of exclude messages being printed. We should only print those with -XX:+PrintCompilation because most of the time they are not relevant and may even hide more important test output if the JTREG option "-Djavatest.maxOutputSize" is set to a low value:

        ### Excluding compile: java.io.OutputStream::flush
        ### Excluding compile: java.nio.ByteBuffer::clear
        ### Excluding compile: java.nio.Buffer::clear
        ### Excluding compile: static com.sun.javatest.Status::encode
        ### Excluding compile: java.io.PrintStream::println
        ### Excluding compile: java.io.PrintStream::newLine
        ### Excluding compile: java.io.BufferedWriter::newLine
        ### Excluding compile: static java.lang.System::lineSeparator
        ### Excluding compile: java.io.PrintStream::flush
        ### Excluding compile: static java.lang.System::exit
        ### Excluding compile: java.lang.Runtime::exit
        ### Excluding compile: static java.lang.Shutdown::<clinit>
        ### Excluding compile: java.lang.Shutdown$Lock::<init>
        ### Excluding compile: java.lang.Shutdown$Lock::<init>
        ### Excluding compile: static java.lang.Shutdown::exit
        ### Excluding compile: static java.lang.Shutdown::sequence
        ### Excluding compile: static java.lang.Shutdown::runHooks
        ### Excluding compile: static java.lang.Shutdown::halt
        ....

              neliasso Nils Eliasson (Inactive)
              thartmann Tobias Hartmann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: