{"push_id":2789364064,"size":1,"distinct_size":1,"ref":"refs/heads/trivial","head":"91b0ecc006c7f2dada86354eca30af6485391e6a","before":"2cf5d63825cb1c0f2a16febe22e9f3374caa4594","commits":[{"sha":"91b0ecc006c7f2dada86354eca30af6485391e6a","author":{"name":"Tim Pepper","email":"4807564e5a18784afafcf20dbdb5591e844b9075@vmware.com"},"message":"storage e2e test: remove race when setting up loopback device\n\nCI has shown occasional failures stemming from an -EBUSY when\ntest/e2e/storage/persistent_volumes-local.go aka \"PersistentVolumes-local\"\nattempts to do losetup.\n\nLooking at the code, it has a clear race between querying the current\nfree loopback device and later explicitly attempting to loopback setup a\nfile at the queried device node.  Losetup nowadays includes the logic to\nhandle this for the user, if the '-f' option is used instead of naming\nthe desired target loopback device explicitly.  It is safe to presume\na suitable losetup is present as the '-f' option is used elsewhere in\nthe test, and it is safe to not record the allocated device, as it is\nalready queried on the fly elsewhere in the test ahead of other commands\nwhich need to know an already created loopback device's node name.\n\nThis patch should result in less flakes for this test case.\n\nSigned-off-by: Tim Pepper <tpepper@vmware.com>","distinct":true,"url":"https://api.github.com/repos/tpepper/kubernetes/commits/91b0ecc006c7f2dada86354eca30af6485391e6a"}]}
{"actor":{"display_login":"tpepper"}}