OK. I'll have to pull down the latest commits and try it again. I'll let you know if I'm still having trouble. Thanks.
Andrew Oberstar On Sat, Jul 14, 2012 at 12:43 AM, Adam Murdoch <[email protected]>wrote: > > On 14/07/2012, at 3:03 PM, Andrew Oberstar wrote: > > I'm working on a couple contributions, and I based my branch of master. > Unfortunately there are some broken tests in master, making it hard for me > to verify that my changes haven't broken anything. In this particular > case, they're unlikely to have, but I can see this being an issue for the > next change I'm going to work on. > > Generally what do you recommend that community members work off of when > trying to contribute? The previous release branch/tag? Master? Something > else? > > > You should be using master. Generally, there should not be any broken > tests in master. Sometimes breakages do slip in, but they are usually > caught fairly quickly at http://builds.gradle.org/overview.html and > fixed. There are also some tests that are a bit too environment specific > and which don't get fixed as quickly as they could ("it works for me"). > > What are the broken tests you are seeing? > > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > >
