[jira] [Created] (YARN-6490) Turn on assign multiple after removing continuous scheduling

Wilfred Spiegelenburg created YARN-6490: --- Summary: Turn on assign multiple after removing continuous scheduling Key: YARN-6490 URL: https://issues.apache.org/jira/browse/YARN-6490 Project:

[jira] [Created] (YARN-6489) Remove continuous scheduling code

Wilfred Spiegelenburg created YARN-6489: --- Summary: Remove continuous scheduling code Key: YARN-6489 URL: https://issues.apache.org/jira/browse/YARN-6489 Project: Hadoop YARN Issue

[jira] [Created] (YARN-6488) Remove continuous scheduling tests

Wilfred Spiegelenburg created YARN-6488: --- Summary: Remove continuous scheduling tests Key: YARN-6488 URL: https://issues.apache.org/jira/browse/YARN-6488 Project: Hadoop YARN Issue

[jira] [Created] (YARN-6487) FairScheduler: remove continuous scheduling (YARN-1010

Wilfred Spiegelenburg created YARN-6487: --- Summary: FairScheduler: remove continuous scheduling (YARN-1010 Key: YARN-6487 URL: https://issues.apache.org/jira/browse/YARN-6487 Project: Hadoop YARN

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

disallowing force pushes to trunk was done back in: * August 2014: INFRA-8195 * February 2016: INFRA-11136 On Mon, Apr 17, 2017 at 11:18 AM, Jason Lowe wrote: > I found at least one commit that was dropped, MAPREDUCE-6673. I was able to > cherry-pick the original

[jira] [Created] (YARN-6486) FairScheduler: Deprecate continuous scheduling in 2.9

Wilfred Spiegelenburg created YARN-6486: --- Summary: FairScheduler: Deprecate continuous scheduling in 2.9 Key: YARN-6486 URL: https://issues.apache.org/jira/browse/YARN-6486 Project: Hadoop YARN

Apache Hadoop qbt Report: trunk+JDK8 on Linux/ppc64le

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/291/ No changes -1 overall The following subsystems voted -1: compile unit The following subsystems voted -1 but were configured to be filtered/ignored: cc javac The following subsystems are

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

I found at least one commit that was dropped, MAPREDUCE-6673.  I was able to cherry-pick the original commit hash since it was recorded in the commit email. This begs the question of why we're allowing force pushes to trunk.  I thought we asked to have that disabled the last time trunk was

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

Hi I had the Apr-14 eve version of trunk on my local machine. I've pushed that. Don't know if anything was committed over the weekend though. Cheers -Arun On Mon, Apr 17, 2017 at 7:17 AM, Anu Engineer wrote: > Hi Allen, > >

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

Hi Allen, https://issues.apache.org/jira/browse/INFRA-13902 That happened with ozone branch too. It was an inadvertent force push. Infra has advised us to force push the latest branch if you have it. Thanks Anu On 4/17/17, 7:10 AM, "Allen Wittenauer" wrote:

Re: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

Looks like someone reset HEAD back to Mar 31. Sent from my iPad > On Apr 16, 2017, at 12:08 AM, Apache Jenkins Server > wrote: > > For more details, see > https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/378/ > > > > > > -1 overall > > > The

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/379/ No changes -1 overall The following subsystems voted -1: docker Powered by Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org