Grant, these are Bisect results, this commit broke TestClusterDumper in tests on windows it seems.. My diagnostic might be wrong but that's what i got.
86e6e1d64901cc0ce436d43a56fcadb8a2cb6c1d is the first bad commit commit 86e6e1d64901cc0ce436d43a56fcadb8a2cb6c1d Author: Grant Ingersoll <[email protected]> Date: Fri Mar 25 14:39:25 2011 +0000 MAHOUT-588: partial commit, not including shell script yet git-svn-id: https://svn.apache.org/repos/asf/mahout/trunk@1085408 13f79535-4 7bb-0310-9956-ffa450edef68 :040000 040000 2b15021b60e0b772e2195948dddb1dd232a790d0 9b163f5489ec03add7726590 13b01c68d86cbaa3 M utils bisect run success On Mon, Mar 28, 2011 at 7:57 PM, Dmitriy Lyubimov <[email protected]> wrote: > doesn't pass on my windows laptop anymore. > > I am running a bisect now to figure where it started failing but it > was ok at least 10 commits earlier. Any idea what commit broke it and > why? > > I guess I can commit with it being broken still but probably if it can > be fixed it better be. > > It also may be because my laptop is running windows (lame i know) but > i'd rather had it fixed on windows too since previously all tests > worked. > > Thanks for any info. > -Dmitriy >
