Hi Amit, I don't see why we need to run a PowerPC build on every test run. It seems excessive, given that most Java code should work on PowerPC without any changes. Why not just run it nightly?
best, Colin On Mon, Aug 22, 2022, at 08:05, Amit Ramswaroop Baheti wrote: > I am planning to raise a PR for re-enabling PowerPC on the pipeline. > > I will be monitoring PowerPC for failures. I hope this resolves the > concern about build failures on PowerPC. Let me know otherwise. > > Thanks, > Amit Baheti > > -----Original Message----- > From: Amit Ramswaroop Baheti <arams...@in.ibm.com> > Sent: 10 August 2022 20:09 > To: dev@kafka.apache.org > Subject: [EXTERNAL] RE: ARM/PowerPC builds > > I looked at the PR failures on PowerPC jenkins node & the issue was due > to few stuck gradle daemons. I could find that using "./gradlew > --status". > After I cleaned them up using "./gradlew --stop", I was able to build & > test existing PR's in the jenkins workspace on that node. > > I also pulled another PR #12488 manually & could execute build and > tests successfully on that node. Further the build and test is > executing within minutes. So no problem on the performance front. > > I am wondering if Apache infra team has any automation to clear stuck > gradle daemons. If not, perhaps we may look at one using cron job and > make such infra issues selfheal. > > I think it should be fine now to re-enable the PowerPC node in the pipeline. > > Thanks, > Amit Baheti > > -----Original Message----- > From: Amit Ramswaroop Baheti <arams...@in.ibm.com> > Sent: 05 August 2022 17:52 > To: dev@kafka.apache.org > Subject: [EXTERNAL] RE: ARM/PowerPC builds > > Hi, > > I am looking into the failures on PowerPC. > > I will share more details once I have something concrete & hopefully we > would be able to enable it again soon. > > -Amit Baheti > > -----Original Message----- > From: Colin McCabe <cmcc...@apache.org> > Sent: 04 August 2022 22:39 > To: dev@kafka.apache.org > Subject: [EXTERNAL] Re: ARM/PowerPC builds > > Hi Matthew, > > Can you open a JIRA for the test failures you have seen on M1? > > By the way, I have an M1 myself. > > best, > Colin > > On Thu, Aug 4, 2022, at 04:12, Matthew Benedict de Detrich wrote: >> Quite happy to have this change gone through since the ARM builds were >> constantly failing however I iterate what Divij Vaidya is saying. I >> just recently got a new MacBook M1 laptop that has ARM architecture >> and even locally the tests fail (these are the same tests that also >> failed in Jenkins). >> >> Should get to the root of the issue especially as more people will get >> newer Apple laptops over time. >> >> -- >> Matthew de Detrich >> Aiven Deutschland GmbH >> Immanuelkirchstraße 26, 10405 Berlin >> Amtsgericht Charlottenburg, HRB 209739 B >> >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen >> m: +491603708037 >> w: aiven.io e: matthew.dedetr...@aiven.io On 4. Aug 2022, 12:36 +0200, >> Divij Vaidya <divijvaidy...@gmail.com>, wrote: >>> Thank you. This would greatly improve the PR experience since now, >>> there is higher probability for it to be green. >>> >>> Side question though, do we know why ARM tests are timing out? Should >>> we start a JIRA with Apache Infra to root cause? >>> >>> — >>> Divij Vaidya >>> >>> >>> >>> On Thu, Aug 4, 2022 at 12:42 AM Colin McCabe <cmcc...@apache.org> wrote: >>> >>> > Just a quick note. Today we committed INVALID URI REMOVED >>> > che_kafka_pull_12380&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=50nG1jjahH >>> > 8a5uFJPfv74FQ5POP1oomXeKf8Xylvgw4&m=g4U2eMxnb6_oWrLqMssiRMCn_beLcy75GeHjl2_RYFce1iI2i2HfDSLLFK8gjKrV&s=7rXLDMIeH-7tYpHu6rFBeRVd8kqK0SMKIgb9_nvr6HI&e= >>> > , "MINOR: Remove ARM/PowerPC builds from Jenkinsfile #12380". This PR >>> > removes the ARM and PowerPC builds from the Jenkinsfile. >>> > >>> > The rationale is that these builds seem to be failing all the time, >>> > and this is very disruptive. I personally didn't see any successes >>> > in the last week or two. So I think we need to rethink this integration a >>> > bit. >>> > >>> > I'd suggest that we run these builds as nightly builds rather than >>> > on each commit. It's going to be rare that we make a change that >>> > succeeds on x86 but breaks on PowerPC or ARM. This would let us >>> > have very long timeouts on our ARM and PowerPC builds (they could >>> > take all night if necessary), hence avoiding this issue. >>> > >>> > best, >>> > Colin >>> > >>> -- >>> Divij Vaidya
