I remember this error was there for more than 6 months. It significantly slows down the progress of collaboration. Then, eventually, the community will develop another habit of ignoring the prebuilds (out of despair).
I am willing to help to get this fixed. Anyone knows who owns and has experience with Yetus environment? On Wed, Dec 2, 2020 at 4:43 PM Jim Brennan <james.bren...@verizonmedia.com> wrote: > This is still happening. > Latest build: > https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/343/#showFailuresLink > > Looks like we are running out of threads in the containers where the unit > tests run. Anyone know where this is setup? > > On Wed, Oct 21, 2020 at 5:51 PM Ahmed Hussein <a...@ahussein.me> wrote: > >> Hey folks, >> >> Yetus has been failing miserably over the last couple of days. >> In the Lastest qbt-report >> < >> https://urldefense.proofpoint.com/v2/url?u=https-3A__ci-2Dhadoop.apache.org_job_hadoop-2Dqbt-2Dtrunk-2Djava8-2Dlinux-2Dx86-5F64_301_artifact_out_patch-2Dunit-2Dhadoop-2Dhdfs-2Dproject-5Fhadoop-2Dhdfs.txt&d=DwIBaQ&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=7Imi06B91L3gbxmt5ChzH4cwlA2_f2tmXh3OXmV9MLw&m=HChJ3ymJ0kOlFyiTBsyRZLs9qcTOQD864ZFb8g7y2CA&s=N-PB427UiouJCuX_U3UbUXvIh2HQTt7VdM2Bs_4XILI&e= >> >, >> hundreds of Junits fail after java failed to acquire resources >> to create new threads. >> >> [ERROR] >> > >> testRecoverAllDataBlocks1(org.apache.hadoop.hdfs.TestReconstructStripedFileWithRandomECPolicy) >> > Time elapsed: 8.509 s <<< ERROR! >> > java.lang.OutOfMemoryError: unable to create new native thread >> >> >> Any thoughts on what could trigger that in the last few days? Do we need >> more resources for the image? >> >> -- >> Best Regards, >> >> *Ahmed Hussein, PhD* >> > -- Best Regards, *Ahmed Hussein, PhD*
