Re: Pre-Commit build is failing

-dev@yetus to bcc, since I think this is a Hadoop issue and not a yetus issue. Please review/commit HADOOP-14686 (which I am providing as a volunteer/contributor on the Hadoop project). On Tue, Jul 25, 2017 at 7:54 PM, Allen Wittenauer wrote: > > Again: just

[Vote] merge feature branch YARN-2915 (Federation) to trunk

Hi all, Per earlier discussion [9], I'd like to start a formal vote to merge feature YARN Federation (YARN-2915) [1] to trunk. The vote will run for 7 days, and will end Aug 1 7PM PDT. We have been developing the feature in a branch (YARN-2915 [2]) for a while, and we are reasonably confident

Re: Pre-Commit build is failing

Again: just grab the .gitignore file from trunk and update it in branch-2.7. It hasn't been touched (outside of one patch) in years. The existing jobs should then work. The rest of this stuff, yes, I know and yes it's intentional. The directory structure was inherited from

Re: Pre-Commit build is failing

Hi, Seems like the issue was incorrect/unclean checkout. I made a few changes[1] to the directories the checkout happens to and it is now running. Of course, this build[2] will take some time to run, but at the moment, it is running maven install. I am not sure who sets up/ manages the jenkins

Re: Pre-Commit build is failing

For anyone looking. I created another job here. [1]. Set it with debug to see the issue. The error is being seen here[2]. >From the looks of it, it looks like, the way the checkout is happening is not very clean. I will continue to look at it, but in case anyone wants to jump in. [1] :

Re: Pre-Commit build is failing

Hi Yetus developers, We cannot build Hadoop branch-2.7 anymore. Here is a recent example of a failed build: https://builds.apache.org/job/PreCommit-HDFS-Build/20409/console It seems the build is failing because Yetus cannot apply the patch from the jira. ERROR: HDFS-11896 does not apply to

[jira] [Created] (YARN-6871) Add a new REST API GetAppReport call lighter and faster than the current one

Giovanni Matteo Fumarola created YARN-6871: -- Summary: Add a new REST API GetAppReport call lighter and faster than the current one Key: YARN-6871 URL: https://issues.apache.org/jira/browse/YARN-6871

[jira] [Created] (YARN-6870) ResourceUtilization/ContainersMonitorImpl is calculating CPU utilization as a float, which is imprecise

Brook Zhou created YARN-6870: Summary: ResourceUtilization/ContainersMonitorImpl is calculating CPU utilization as a float, which is imprecise Key: YARN-6870 URL: https://issues.apache.org/jira/browse/YARN-6870

[jira] [Created] (YARN-6869) Resources.lessThan() et al should not use ResourceCalculator.compare()

Daniel Templeton created YARN-6869: -- Summary: Resources.lessThan() et al should not use ResourceCalculator.compare() Key: YARN-6869 URL: https://issues.apache.org/jira/browse/YARN-6869 Project:

[jira] [Created] (YARN-6868) Add test scope to certain entries in hadoop-yarn-server-resourcemanager pom.xml

Ray Chiang created YARN-6868: Summary: Add test scope to certain entries in hadoop-yarn-server-resourcemanager pom.xml Key: YARN-6868 URL: https://issues.apache.org/jira/browse/YARN-6868 Project: Hadoop

[jira] [Created] (YARN-6867) AbstractYarnScheduler reports the configured maximum resources, instead of the actual, even after the configured waittime

Muhammad Samir Khan created YARN-6867: - Summary: AbstractYarnScheduler reports the configured maximum resources, instead of the actual, even after the configured waittime Key: YARN-6867 URL:

[jira] [Resolved] (YARN-6822) TestContainerManagerSecurity tests fail on trunk

[ https://issues.apache.org/jira/browse/YARN-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YARN-6822. - Resolution: Duplicate Fixed by YARN-6150. Please feel free to reopen this if the error is not