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

Need more precise control on build system logging

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P3
    • 10
    • 10
    • infrastructure
    • None
    • b04
    • generic

    Description

      1. Would like to be able to log recipe execution times (profile data) not only with 'trace' log level but with any log level.
      2. Would like to have logged recipe execution times be a part of build log.
      3. Would like to measure shell command execution times in environments without GNU 'time' utility.

      Proposed changes discussed with Magnus and Erik:
      1. Add new "profile" and "profile-to-log" log options:
      LOG=trace - trace recipe executions, but doesn't collect profile data.
      LOG=trace,profile - trace recipe executions and collect profile data in separate file.
      LOG=trace,profile-to-log - trace recipe executions, collect profile data in separate file, append contents of file with profile data to build log.

       LOG=profile-to-log and LOG=profile,profile-to-log are equivalent.

      Similarly, "profile" and "profile-to-log" mods can be used with other log levels.

      2. Rename $(OUTPUT_ROOT)/build-trace-time.log in $(OUTPUT_ROOT)/build-profile.log.

      3. Rename $(JDK)/common/bin/shell-tracer.sh $(JDK)/common/bin/shell-profiler.sh . Rework the script so that it log full shell command line (currently it doesn't log path to shell executing the command) and emulate GNU time utility if 'flock' utility is available.

      4. Add lookup for 'flock' utility to configure script.

      Attachments

        Activity

          People

            asemenyuk Alexey Semenyuk
            asemenyuk Alexey Semenyuk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: