{"push_id":655449188,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"71c1a7ea7f28a4e4bf3412af228524a28226ebeb","before":"a242ceaa0967a72dee55ef6a2cec05c78526d33c","commits":[{"sha":"d2c4ee37c6a4114b33a915b7dae6de70e27e7965","author":{"email":"dc73d0991b982a8303e713ef531a313af77e242a@gmail.com","name":"Brian Goff"},"message":"Fix LXC stop signals\n\n`lxc-stop` does not support sending arbitrary signals.\nBy default, `lxc-stop -n <id>` would send `SIGPWR`.\nThe lxc driver was always sending `lxc-stop -n <id> -k`, which always\nsends `SIGKILL`. In this case `lxc-start` returns an exit code of `0`,\nregardless of what the container actually exited with.\nBecause of this we must send signals directly to the process when we\ncan.\n\nAlso need to set quiet mode on `lxc-start` otherwise it reports an error\non `stderr` when the container exits cleanly (ie, we didn't SIGKILL it),\nthis error is picked up in the container logs... and isn't really an\nerror.\n\nAlso cleaned up some potential races for waitblocked test.\n\nSigned-off-by: Brian Goff <cpuguy83@gmail.com>","distinct":true,"url":"https://api.github.com/repos/noironetworks/docker/commits/d2c4ee37c6a4114b33a915b7dae6de70e27e7965"},{"sha":"71c1a7ea7f28a4e4bf3412af228524a28226ebeb","author":{"email":"2043cda4df124b840b98ee1c4307c199042efdf7@gmail.com","name":"Alexander Morozov"},"message":"Merge pull request #13017 from cpuguy83/12859_fix_lxc_wait_exitcodes\n\nFix LXC stop signals","distinct":true,"url":"https://api.github.com/repos/noironetworks/docker/commits/71c1a7ea7f28a4e4bf3412af228524a28226ebeb"}]}