MSBuild parser multiplies warnings when compiling with /MP

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When using switch /MP with MSBuild to enable multi-threaded compilation, the MSVC compiler will output a log line like

      195>c:\jenkins\workspace\develop\foo.h(76): warning C4100: 'Id': unreferenced formal parameter (compiling source file bar.cpp) [C:\jenkins\workspace\develop\project.vcxproj]
      

      for warnings in header files. These lines are repeated for every translation unit the header file is included in. They will only differ in the translation unit's file name (bar.cpp in the above example) and always refer to the same cause in the header file (foo.h in the above example).
      However, Jenkins treats each of these log lines as separate warnings. So if the same header is included in two different translation units Jenkins will report each warning in this header twice.
      This breaks quality gates when comparing builds using /MP with builds that don't.

            Assignee:
            Ulli Hafner
            Reporter:
            Marne
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: