On Wed, Feb 22, 2012 at 7:53 PM, Santhosh Srinivasan <[email protected]> wrote: > AFAIK there are no Mac installations of the Hadoop, Pig, Oozie, etc. Given > that the cost of catching a failing unit test during release time (given that > we don't have CI in Apache) is fairly high. Most of you must have noticed > unit test case failures on the recent release.
CI resources are available, if interest drives someone to work on it. What makes a failing unit test expensive during release time? > Use of a Mac (or Windows ;) is a convenience that we can't forego. What are > the best practices in the other Apache projects? In Hadoop, Windows+Cygwin was supported while developers who used it cared to fix those bugs. When they didn't, some unit tests consistently failed on that platform. Most projects either rely on CI or an auditing phase during release. It's not the end of the world if corners of trunk, or any development branch, are broken for awhile. YMMV, but nightly builds are usually sufficient to catch regressions. Does this need a policy? Surely no release would go out if it didn't work on Linux. -C > Santhosh > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Roman > Shaposhnik > Sent: Wednesday, February 22, 2012 4:34 PM > To: [email protected] > Cc: Mohammad Islam > Subject: Re: Feedback requested: Building in Linux/Mac/Doesn't matter > > On Wed, Feb 22, 2012 at 4:22 PM, Alejandro Abdelnur <[email protected]> wrote: >> To run tests on a given platform? No, but if doing hadoop native >> stuff, only linux is supported at the moment. > > I must add to that: there is absolutely a hard requirement for test-patch not > failing to build. And that build is a Linux one. > > Thanks, > Roman.
