You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benno Evers (JIRA)" <ji...@apache.org> on 2018/01/24 12:42:00 UTC

[jira] [Created] (MESOS-8482) Signed/Unsigned comparisons in tests

Benno Evers created MESOS-8482:
----------------------------------

             Summary: Signed/Unsigned comparisons in tests
                 Key: MESOS-8482
                 URL: https://issues.apache.org/jira/browse/MESOS-8482
             Project: Mesos
          Issue Type: Bug
            Reporter: Benno Evers


Many tests in mesos currently have comparisons between signed and unsigned integers, eg
{noformat}
    ASSERT_EQ(4, v1Response->read_file().size());
{noformat}
or comparisons between values of different enums, e.g. TaskState and v1::TaskState:
{noformat}
  ASSERT_EQ(TASK_STARTING, startingUpdate->status().state());
{noformat}
Usually, the compiler would catch these and emit a warning, but these are currently silenced because gtest headers are included using the `-isystem` command line flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)