Hi Adam,
Thanks for putting so much effort for making ptests better. Really appreciate
this.
Regards,
Deepak
On 5/14/18, 11:47 AM, "Adam Szita" wrote:
This is now committed and has been deployed some hours ago - don't worry if
you see your job failed I resubmitted everything from the
This is now committed and has been deployed some hours ago - don't worry if
you see your job failed I resubmitted everything from the queue.
I will be keeping an eye on how ptest works after this change.
Thanks,
Adam
On 2 May 2018 at 17:34, Adam Szita wrote:
> I have a patch available for the v
I have a patch available for the voted version at
https://issues.apache.org/jira/browse/HIVE-19077. Let me know what you
think.
On 27 April 2018 at 15:55, Adam Szita wrote:
> Thanks to all for the responses.
> As I see it, option 3 is the winning one. Next week I'm going start
> working on this
Thanks to all for the responses.
As I see it, option 3 is the winning one. Next week I'm going start working
on this one then (unless any objections of course).
Adam
On 26 April 2018 at 05:48, Deepak Jaiswal wrote:
> +1 for option 3. Thanks Adam for taking this up again.
>
> Regards,
> Deepak
>
+1 for option 3. Thanks Adam for taking this up again.
Regards,
Deepak
On 4/25/18, 4:54 PM, "Thejas Nair" wrote:
Option 3 seems reasonable. I believe that used to be the state a while
back (maybe 12 months back or so).
When 2nd ptest for same jira runs, it checks if the latest patc
Option 3 seems reasonable. I believe that used to be the state a while
back (maybe 12 months back or so).
When 2nd ptest for same jira runs, it checks if the latest patch has
already been run.
On Wed, Apr 25, 2018 at 7:37 AM, Peter Vary wrote:
> I would vote for version 3. It would solve the big
I would vote for version 3. It would solve the big patch problem, and removes
the unnecessary test runs too.
Thanks,
Peter
> On Apr 25, 2018, at 11:01 AM, Adam Szita wrote:
>
> Hi all,
>
> I had a patch (HIVE-19077) committed with the original aim being the
> prevention of wasting resources w
Hi all,
I had a patch (HIVE-19077) committed with the original aim being the
prevention of wasting resources when running ptest on the same patch
multiple times:
It is supposed to manage scenarios where a developer uploads
HIVE-XYZ.1.patch, that gets queued in jenkins, then before execution
HIVE-X
Would it be possible to add patch name validation when it gets added to the
queue?
Currently I think it fails when the bot gets to the patch if it’s not named
correctly.
More common for branch patches
On 4/20/18, 8:20 AM, "Zoltan Haindrich" wrote:
Hello,
Some time ago the ptest q
