Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-229

rwlock-perf doesn't work in a VMware VM

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: M4
    • Fix Version/s: None
    • Component/s: perf
    • Labels:
      None

      Description

      Here's what I get when I run it:

              Test   Threads  Cycles
      ------------------------------
      WARNING: Logging before InitGoogleLogging() is written to STDERR
      F0412 19:52:08.029077 25130 locks.h:145] Check failed: (*__errno_location ()) == 0 (2 vs. 0) No such file or directory
      *** Check failure stack trace: ***
      Aborted (core dumped)
      

      After some digging, the problem is in base::NumCPUs, which, by the way of InitializeSystemInfo, fails to open /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq and /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq (the /cpufreq subdir doesn't exist in my VM). These failures are non-fatal, but InitializeSystemInfo doesn't reset errno before returning, and locks.h complains about that.

      I didn't see any open issues filed about this in gperftools. Not sure if we care enough to file one, or whether this is a bug in our code (locks.h).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adar Adar Dembo
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: