If the goal is to optimize multiple patch submissions, instead of skipping one,
perhaps it should take the latest patch from the jira and cancel future ones
runs already in the queue.
On 4/13/18, 11:16 AM, "Deepak Jaiswal" <djais...@hortonworks.com> wrote:
I reopened HIVE-19077 to remove the future instance instead of the current
one.
On 4/13/18, 11:10 AM, "Deepak Jaiswal" <djais...@hortonworks.com> wrote:
Hi,
It seems someone committed a patch to modify ptests. I see this on the
ptest console output,
“Checking PreCommit-HIVE-Build queue...
PreCommit-HIVE-Build has the following jira(s) in queue: [18845, 19161,
19054, 19161, 19126, 19184, 18652, 19184, 19187, 19175, 18902, 19104, 16041,
12369, 12192, 18862, 19009, 18739, 19104, 19167, 18910, 16144, 19106, 18816,
19133, 19162, 18986, 19191, 17645, 19186, 18609, 18469, 17824, 19048, 18252,
18252, 19001, 18739, 18915, 19154, 19096]
Skipping ptest execution, as HIVE-18910 is scheduled in queue in the
future too.
“
After waiting for 2 days I get to see this which does not make any
sense. The queue is so long and then you get pushed back? Worst, I am not even
in the queue anymore.
I cant find the JIRA which did this. So I request the developer who did
this to revert it back and rework on it to remove the future instance from the
queue. If you have time constraint, please assign it to me.
Regards,
Deepak
