On Thu, Dec 29, 2016 at 11:13 AM, Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Thu, Dec 29, 2016 at 3:37 AM, James Almer <jamr...@gmail.com> wrote: >> On 12/28/2016 8:34 PM, Michael Niedermayer wrote: >>> This may fix the failures on windows >> >> Not sure what failures this is about > > This failure, which keeps popping up sporadically since > c4152fc42e480c41efb7f761b1bbe5f0bc43d5bc, because Windows uses > CLOCKS_PER_SEC=1000 > > http://fate.ffmpeg.org/report.cgi?time=20161228142737&slot=x86_64-msvc14-windows-native >
Its not isolated to windows either, OSX/Darwin has the same issue: http://fate.ffmpeg.org/report.cgi?time=20161229055656&slot=i386-darwin-clang-3.8-O3 http://fate.ffmpeg.org/report.cgi?time=20161229052603&slot=i386-darwin-gcc-6 - Hendrik _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
