Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26441

GoogleTest failure interpreted as compiler error on VC10_64

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • warnings-plugin
    • None
    • Jenkins 1.588
      Warnings-Plugin 4.45
      googletest 1.6.0
      Windows 7 VC10_64

      We are using the warnings-plugin after a compilation pass with VC10_64 and a subsequent step of running a google-test binary. The gtest produces a test failure using the EXPECT_LE macro. The error message is printed below. Regrettably this is interpreted as compiler error by the warnings-plugin.

      The confusing part of this is that on Linux/OSX gtest prints the same message, but with "error" being replaced by "Failure". On those platforms the warnings-plugin works as expected.

      I don't know how to discriminate this from a compiler message. Maybe by looking for "Expected:" after the error?

      [  FAILED  ] allCases/ReferenceCaseTest.ROIRequirementsTest/25, where GetParam() = (19, 1) (11760 ms)
[ RUN      ] allCases/ReferenceCaseTest.ROIRequirementsTest/29
C:\Program Files (x86)\Jenkins\jobs\MyJob\workspace\MyProject\testing\regression_tests\BackToBackTest\ROIRequirements.cpp(168): error: Expected: (xEdgeLength) <= (maxEdgeLength), actual: 150.781 vs 150

          [JENKINS-26441] GoogleTest failure interpreted as compiler error on VC10_64

          Ruben Stein created issue -
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 160508 ] New: JNJira + In-Review [ 196463 ]

            drulli Ulli Hafner
            rst Ruben Stein
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: