{"push_id":2836610023,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"3c8e5acffcff8b18b7242d262965604b507e0c36","before":"d27624a7e137c5b1a0460ddf201ef7081b7413ff","commits":[{"sha":"3c8e5acffcff8b18b7242d262965604b507e0c36","author":{"name":"Anton Bachin","email":"c2e7f2427ccbce9d1b2f68285e9ea79a19b32340@yahoo.com"},"message":"Fix check for existing bisectWXYZ.out files\n\nBefore this fix, Bisect would keep trying to create these files, with\ndifferent suffixes, if creating the previous ones failed for *any*\nreason. This included the parent directory not existing, in which case\nnone of the files could be created anyway. This would send Bisect into\nan infinite loop.\n\nNow, Bisect continues trying to create files only if the previous files\ncould not be created specifically because they already existed.\n\nUnfortunately, the Bisect runtime picks up a Unix dependency, because\nthe functions in Sys and Pervasives don't seem to provide a reliable way\nof determining why file creation failed. The Sys_error exception raised\nby open_out_gen carries a string as payload, which doesn't seem to be as\nfuture-proof as the Unix.EEXIST payload of Unix_error from\nUnix.openfile.\n\nResolves #175.","distinct":true,"url":"https://api.github.com/repos/aantron/bisect_ppx/commits/3c8e5acffcff8b18b7242d262965604b507e0c36"}]}
{"actor":{"display_login":"aantron"}}