When running tests from device_cloud_policy_manager_chromeos_unittest.cc, the following GMOCK warnings are appearing:

DeviceCloudPolicyManagerChromeOSTest.EnrolledDevice:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

DeviceCloudPolicyManagerChromeOSTest.UnmanagedDevice:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.Success/0:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.Success/1:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.Reenrollment/0:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.Reenrollment/1:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.UnregisterSucceeds/0
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.UnregisterSucceeds/1:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.UnregisterFails/0:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()

Cert/DeviceCloudPolicyManagerChromeOSEnrollmentTest.UnregisterFails/1:
GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnDeviceCloudPolicyManagerConnected()


This issue doesn't seem to influence the tests behavior in any way. But this, probably, needs to be fixed from the sanity perspective.