Closed corruptmemory closed 9 years ago
The real test is if Travis agrees with me.
maybe add some logging to each step in the sequence of events that's supposed to happen, and see if we can understand what goes wrong?
That's such a crazy idea it might just work! :-)
Yeah, going to get around to that as well. One concern is that this may be some kind of subtle timing error that the extra logging may mask.
The test is currently failing for openjdk 6; I'm going to install that locally to see if I can make it happen on my machine.
Well, found the issue. Something about the test is broken. Nothing related to JDK versions or anything. Will fix sometime today.
Nope, not just a wrong test. Wrong code. HA! Classic problem in code evolution: there is a small amount of code left over from an earlier version of the SbtConnectionProxy that is now wrong. Yay tests! :-)
I think this should have better inter-thread sharing sematics.