We need to investigate and find out root cause of these failures. If its determined that its a corner case and fix is non-trivial then we may release note it under known issues. But ideally we should fix these failures. Cutting a branch should make it easier since branch is expected to receive lot less commits as compared to master so it should be faster to stabilize branch.
On Fri, Apr 6, 2018 at 10:49 AM, Eugene Koifman <ekoif...@hortonworks.com> wrote: > Cutting the branch before the tests are stabilized would mean we have to > fix them in 2 places. > > On 4/6/18, 10:05 AM, "Thejas Nair" <thejas.n...@gmail.com> wrote: > > That needs to be cleaned up. There are far too many right now, its > just not handful of flaky tests. > > > On Fri, Apr 6, 2018 at 2:48 AM, Peter Vary <pv...@cloudera.com> wrote: > > Hi Team, > > > > I am new to the Hive release process and it is not clear to me how > the failing tests are handled. Do we plan to fix the failing tests before > release? Or it is accepted to cut a new major release with known test > issues. > > > > Thanks, > > Peter > > > >> On Apr 5, 2018, at 8:25 PM, Vineet Garg <vg...@hortonworks.com> > wrote: > >> > >> Hello, > >> > >> I plan to cut off branch for Hive 3.0.0 on Monday (9 April) since > bunch of folks have big patches pending. > >> > >> Regards, > >> Vineet G > >> > >>> On Apr 2, 2018, at 3:14 PM, Vineet Garg <vg...@hortonworks.com> > wrote: > >>> > >>> Hello, > >>> > >>> We have enough votes to prepare a release candidate for Hive > 3.0.0. I am going to cutoff a branch in a day or two. I’ll send an email as > soon as I have the branch ready. > >>> Meanwhile there are approximately 69 JIRAs which are currently > opened with fix version 3.0.0. I’ll appreciate if their respective owners > would update the JIRA if it is a blocker. Otherwise I’ll update them to > defer the fix version to next release. > >>> > >>> Regards, > >>> Vineet G > >>> > >> > > > > > >
