{"action":"opened","issue":{"url":"https://api.github.com/repos/mesos/chronos/issues/682","repository_url":"https://api.github.com/repos/mesos/chronos","labels_url":"https://api.github.com/repos/mesos/chronos/issues/682/labels{/name}","comments_url":"https://api.github.com/repos/mesos/chronos/issues/682/comments","events_url":"https://api.github.com/repos/mesos/chronos/issues/682/events","html_url":"https://github.com/mesos/chronos/issues/682","id":155288456,"number":682,"title":"Retain most recent job statusCode returned, and expose in hash returned by e.g. /status/jobs","user":{"login":"avi8tr","id":8441761,"avatar_url":"https://avatars.githubusercontent.com/u/8441761?v=3","gravatar_id":"","url":"https://api.github.com/users/avi8tr","html_url":"https://github.com/avi8tr","followers_url":"https://api.github.com/users/avi8tr/followers","following_url":"https://api.github.com/users/avi8tr/following{/other_user}","gists_url":"https://api.github.com/users/avi8tr/gists{/gist_id}","starred_url":"https://api.github.com/users/avi8tr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/avi8tr/subscriptions","organizations_url":"https://api.github.com/users/avi8tr/orgs","repos_url":"https://api.github.com/users/avi8tr/repos","events_url":"https://api.github.com/users/avi8tr/events{/privacy}","received_events_url":"https://api.github.com/users/avi8tr/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-17T15:24:43Z","updated_at":"2016-05-17T15:24:43Z","closed_at":null,"body":"When an async job writes its statusCode to Chronos' /scheduler/task/<task id> endpoint prior to exiting, Chronos interprets any nonzero statusCode as failure.  Currently, however, the statusCode itself is logged (if INFO logging is enabled) and discarded, depriving the REST client of failure-related information relayed by the job in the statusCode.  Alternative mechanisms such as mis-using the job progress reporting mechanism are (much) more complicated and susceptible to races. Please retain the statusCode for the most recent execution and expose it in hashes of the job status query endpoints.\r\n"}}