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

"top" command during jtreg failure handler does not display CPU usage on OSX

    XMLWordPrintable

Details

    • b27

    Backports

      Description

        In test/failure_handler/src/share/conf/mac.properties we have:

        process.top.app=top
        process.top.args=-l 1

        So top is run with the "-l 1" args, causing it to do one iteration and then exit. Unfortunately the first iteration always shows all 0's for CPU usage. If you do at least 2 iterations, you do see the proper CPU usage on the 2nd iteration. The user just needs to know to scroll down to see it. I suggest we start using "-l 2" unless someone has a better idea.

        BTW, for proper CPU usage you can instead look at the failure handler "ps" output, which seems to be correct. But it is nice to have "top" produce the correct output so all the CPU hogs are at the top of the list.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8326727 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8326931 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8327013 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8328052 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8328053 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8328054 "top" command during jtreg failure handler does not display CPU usage on OSX

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved
            links to

            Commit Commit openjdk/jdk11u-dev/a097faa9

            Commit Commit openjdk/jdk17u-dev/09ebd1cc

            Commit Commit openjdk/jdk21u-dev/2a6688f6

            Commit Commit openjdk/jdk/8be3e392

            Review Review openjdk/jdk11u-dev/2597

            Review Review openjdk/jdk17u-dev/2286

            Review Review openjdk/jdk21u-dev/347

            Review Review openjdk/jdk/16915

            Activity

              People

                lmesnik Leonid Mesnik
                cjplummer Chris Plummer
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: