{"push_id":578776935,"size":1,"distinct_size":1,"ref":"refs/heads/strict-test-environment","head":"ed345fb18ee9d003f30884b696628b75380a426a","before":"76b5771c95a4e7cb2ebfc14158c5199c3c6aeb63","commits":[{"sha":"ed345fb18ee9d003f30884b696628b75380a426a","author":{"email":"4b2b69742da531f1900c4c4748d7a0ecda59626a@gmail.com","name":"Tianon Gravi"},"message":"Run tests in stricter environment\n\nUse `env -i` to very explicitly control exactly which environment variables leak into our tests.  This enforces a clean separation of \"build environment knobs\" versus \"test suite knobs\".\n\nThis also includes a minor tweak to how we handle starting our integration daemon, especially to catch failure to start sooner than failing tests.\n\nSigned-off-by: Andrew \"Tianon\" Page <admwiggin@gmail.com>","distinct":true,"url":"https://api.github.com/repos/tianon/docker/commits/ed345fb18ee9d003f30884b696628b75380a426a"}]}