My JIRAs also got disappeared. But, what other developers which have no access to submit manually on builds.apache.org will be doing?
Thanks, Igor. 2018-05-03 22:47 GMT+03:00 Prasanth Jayachandran < pjayachand...@hortonworks.com>: > My JIRAs also got disappeared mysteriously and had to manually submit the > patch. > +1 on making it manual (atleast this will make the patch not disappear and > is more predictable/no babysitting). > > Thanks > Prasanth > > > On May 3, 2018, at 12:40 PM, Sergey Shelukhin <ser...@hortonworks.com> > wrote: > > > > Ping? I just had 3-4 JIRAs again disappear from the queue mysteriously, > for the 2nd or 3rd time in one week. > > > > Given that there doesn’t appear to be major interest in improving the > script in the community (other than some minor changes), should we just > nuke it and have manual submission w/2 fields, a patch file and jira > number? That way the tracking at least can be improved. And the patch > choice to run or not run. > > This would take less time than trying to appease the fickle spirits of > HiveQA as it is now. And also probably result in somewhat shorter queues. > > > > From: Sergey Shelukhin <ser...@hortonworks.com<mailto: > ser...@hortonworks.com>> > > Date: Thursday, April 26, 2018 at 17:57 > > To: "dev@hive.apache.org<mailto:dev@hive.apache.org>" < > dev@hive.apache.org<mailto:dev@hive.apache.org>> > > Subject: switching HiveQA to manual submission? > > > > Given the constant cluster.... with HiveQA, namely queue constantly > losing or not picking up patches for whatever reason (not limited to dedup > - I uploaded some patches today where there’s only one attached to the JIRA > and still it didn’t get in the queue or got removed) I wonder if we should > add manual submission option to HiveQA. Or make it the only option actually. > > That way one can target a specific file and get a specific job link back > that won’t got anywhere (one can hope)... > >
