There are two places where you can tune the memory [1] & [2] I haven't checked again, but I think it is the same old problem, I mentioned that in [3] in the last paragraph where there was some windows failure report. I did drop a comment [4] on that PR telling about those issues, there were some comments on the Jira but I didn't follow...
So, technically it should be an HDFS induced mess, else I would have reverted by now :-) Good Luck!!! -Ayush [1] https://github.com/apache/hadoop/blob/2ee0bf953492b66765d3d2c902407fbf9bceddec/hadoop-project/pom.xml#L172 [2] https://github.com/apache/hadoop/blob/2ee0bf953492b66765d3d2c902407fbf9bceddec/dev-support/docker/Dockerfile#L77 [3] https://lists.apache.org/thread/hmzl61ow0sbs10p0hky17xxhsggbhc3g [4] https://github.com/apache/hadoop/pull/6664#issuecomment-2082356393 On Fri, 7 Jun 2024 at 08:04, Xiaoqiao He <hexiaoq...@apache.org> wrote: > > Thanks Steve. Try to trigger CI manually and let's wait what it will say. > BTW, the flaky tests seem not related to UT logic itself, but most of them > throw OOM. Not sure if @Ayush Saxena knows how to re-config or tune > the memory of Yetus? > > Best Regards, > - He Xiaoqiao > > On Fri, Jun 7, 2024 at 3:59 AM Steve Loughran <ste...@cloudera.com.invalid> > wrote: >> >> PR's which trigger hdfs builds seem to hit a lot of hdfs test failures >> https://github.com/apache/hadoop/pull/6675 >> >> Are these regressions or are the tests flaky? >> >> I don't want commit patches which break things, yet hdfs tests seem >> unreliable and so I'm dangerously tempted to +1 anyway... --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
