Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-2503

Check TaskStatus::Reason in tests

    XMLWordPrintableJSON

Details

    • Epic
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • None
    • None
    • test
    • Check TaskStatus::Reason in tests

    Description

      We have a number of reasons for task status updates, but we do not test all of them. On the other side, some failures that we check in our tests do not have reason field set. It would be nice to have a check for state, reason and source for every failed or lost task. E.g.

        AWAIT_READY(status4);
        EXPECT_EQ(TASK_LOST, status4.get().state());
        EXPECT_EQ(TaskStatus::SOURCE_SLAVE, status4.get().source());
        EXPECT_EQ(TaskStatus::REASON_EXECUTOR_TERMINATED, status4.get().reason());
      

      To solve this problem several changes in different parts of the codebase should be made. Hence we make an epic out of it and do it step-by-step.

      Attachments

        Activity

          People

            dyatlov Andrey Dyatlov
            alexr Alex R
            dhamon@twitter.com dhamon@twitter.com
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: