{"push_id":799782412,"size":1,"distinct_size":1,"ref":"refs/heads/patch-1","head":"6215563857c21d7ef2878565e9e8b459196b7004","before":"82c3dc039e68048bfe0517a0c831fe2e2043daf5","commits":[{"sha":"6215563857c21d7ef2878565e9e8b459196b7004","author":{"email":"8ad9dde6e9fd2cac85bf93d43745bf114d9dff6e@gmail.com","name":"Rick Moritz"},"message":"Fix time-dependant scheduling test\n\ntest-schedule can fail when it starts late in a second, as the result will then return the next second due to in-system delays (particularly cron not reacting in time to config.put(cron, null)).\r\nAdding an additional waiting second before measuring dateFinished allows us to take a value that is independent of a possible lagging execution, waiting another second makes sure that the process has properly stopped.\r\n\r\nAlternatively, we can test the time and make sure to not write to cron when just before the full second - that would be quicker (less waiting) but slightly more hacky.\r\n\r\nPlease review.","distinct":true,"url":"https://api.github.com/repos/RPCMoritz/incubator-zeppelin/commits/6215563857c21d7ef2878565e9e8b459196b7004"}]}