Hi Colin, As discussed with Divij according the point 2 mentioned in the last comment I updated the Test Plan to run job for every merge to trunk.
Thanks, Vaibhav Nazare -----Original Message----- From: Divij Vaidya <divijvaidy...@gmail.com> Sent: Monday, July 24, 2023 6:14 PM To: dev@kafka.apache.org Subject: [EXTERNAL] Re: [DISCUSS] KIP-942: Add Power(ppc64le) support Hi Vaibhav 1. Could you please add the details that we discussed here in this thread to the KIP (e.g. why is it safe to add this infra now and which other projects are using it). This would help to have KIP as a source of record if someone wants to read about this decision in future. 2. Given that we merge ~5-6 commits a day to trunk, I would be inclined towards running this infra on every merge to trunk (instead of a daily run as I suggested earlier). It won't be run for every PR though. These are the last two thoughts from my side. Otherwise, it looks good. -- Divij Vaidya On Mon, Jul 10, 2023 at 7:09 PM Vaibhav Nazare <vaibhav.naz...@ibm.com.invalid> wrote: > > Hi Colin and Mickael, > > Yes I agree we don't have to run on every build , may be as mentioned we can > run the job once/twice a day at specific time. > According the test plan the tests which I mentioned are not specific to > ppc64le , I was running tests on the trunk branch which were common across > platforms on that specific commit and I have removed the table and mentioned > the test plan accordingly when to run the jobs. > > > > -----Original Message----- > From: Mickael Maison <mickael.mai...@gmail.com> > Sent: Tuesday, July 4, 2023 3:12 PM > To: dev@kafka.apache.org > Subject: [EXTERNAL] Re: [DISCUSS] KIP-942: Add Power(ppc64le) support > > Hi, > > Thanks for the KIP! > In the Test Plan section you mentioned a few unit and integration tests are > failing. Are these flaky tests or did you find issues related to ppc64le? If > they are just flaky tests, I think we can remove that table and instead > describe how often we intend to run the tests in the CI. > > Thanks, > Mickael > > On Tue, Jul 4, 2023 at 12:04 AM Colin McCabe <cmcc...@apache.org> wrote: > > > > I agree with Divij. A nightly Apache Kafka build for PowerPC would be > > welcome. But it shouldn't run on every build, since the extra time and > > complexity would not be worth it. > > > > By the way, are there any features or plugins we don't intend to support on > > PPC? If there are, this KIP would be a good place to spell them out. > > > > Naively, I would think all of our Java and Scala code should work on > > PPC without changes. However, there may be library dependencies that > > don't exist on PPC. (We have to remember that the last desktop > > PowerPC chip that an average user could buy shipped in 2005....) > > > > best, > > Colin > > > > > > On Mon, Jun 19, 2023, at 23:12, Vaibhav Nazare wrote: > > > Thank you for response Divij. > > > > > > 1. We are going to use ASF infra provided nodes for better > > > availability and stability as there are 3 power9 nodes managed > > > officially by ASF infra team themselves. > > > Ref: > > > INVALID URI REMOVED > > > rg_jira_browse_INFRA-2D24663&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=s > > > 9I > > > 3h_d72lHAurpHrTUoOkX8ByFHVUGD0XU1PTKfCiw&m=wok2fkRzJGACiUg-o6hyaJP > > > 11 > > > WLbfqYbH78J2VuRdvseBKrVLuXW9PtUJqs9BWO4&s=EeWMMaaUqDLlqUjJmw3_ouI9 > > > lt > > > 4B_EUGyH8OZ_VTIRE&e= > > > INVALID URI REMOVED. > > > apache.org_view_Shared-2520-2D-2520ppc64le-2520nodes_&d=DwIFaQ&c=j > > > f_ > > > iaSHvJObTbx-siA1ZOg&r=s9I3h_d72lHAurpHrTUoOkX8ByFHVUGD0XU1PTKfCiw& > > > m= > > > wok2fkRzJGACiUg-o6hyaJP11WLbfqYbH78J2VuRdvseBKrVLuXW9PtUJqs9BWO4&s > > > =O R-kg7uZdehAVxU7TdCUruDpGb0yOAEa0wW2dC3P3yU&e= > > > previously used power node details for apache/kafka CI: > > > RAM- 16GB > > > VCPUs- 8 VCPU > > > Disk- 160GB > > > for shared VMs we need to check with ASF infra team to provide > > > details > > > > > > 2. We can run nightly builds once or twice in a day on specific > > > period of time instead of every commit 3. apache/camel INVALID URI > > > REMOVED > > > rg_job_Camel_job_el_&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=s9I3h_d72lHAurpHrTUoOkX8ByFHVUGD0XU1PTKfCiw&m=wok2fkRzJGACiUg-o6hyaJP11WLbfqYbH78J2VuRdvseBKrVLuXW9PtUJqs9BWO4&s=J35xYPMn5tCJRn91aARKgyiwas_cu4RGeSsh50tV4GI&e= > > > has already enabled CI for power platform they are using same H/W > > > resources as > > > RAM- 16GB > > > VCPUs- 8 VCPU > > > Disk- 160GB > > > > > > -----Original Message----- > > > From: Divij Vaidya <divijvaidy...@gmail.com> > > > Sent: Monday, June 19, 2023 10:20 PM > > > To: dev@kafka.apache.org > > > Subject: [EXTERNAL] Re: [DISCUSS] KIP-942: Add Power(ppc64le) > > > support > > > > > > Thank you for the KIP Vaibhav. > > > > > > 1. Builds for power architecture were intentionally disabled in > > > the past since the infrastructure was flaky [1]. Could you please > > > add to the KIP on what has changed since then? > > > 2. What do you think about an alternative solution where we run a > > > nightly build for this platform instead of running the CI with > > > every PR/commit? > > > 3. To bolster the case for this KIP, could you please add > > > information from other Apache projects who are already running CI > > > for this platform? Is their CI stable on Apache Infra hosts? > > > > > > > > > [1] > > > INVALID URI REMOVED > > > he_kafka_pull_12380&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=s9I3h_d72l > > > HA > > > urpHrTUoOkX8ByFHVUGD0XU1PTKfCiw&m=wok2fkRzJGACiUg-o6hyaJP11WLbfqYb > > > H7 > > > 8J2VuRdvseBKrVLuXW9PtUJqs9BWO4&s=Wo7q9L9UOHo8AkRRwIFG9570Y4isqaxmh > > > IY > > > W0wwVspk&e= > > > > > > -- > > > Divij Vaidya > > > > > > > > > > > > On Mon, Jun 19, 2023 at 12:30 PM Vaibhav Nazare > > > <vaibhav.naz...@ibm.com.invalid> wrote: > > > > > >> > > >> INVALID URI REMOVED > > >> confluence_display_KAFKA_KIP-2D942-253A-2BAdd-2BPower-2528ppc64le > > >> -2 > > >> 529 > > >> -2Bsupport&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=s9I3h_d72lHAurpHrT > > >> Uo > > >> OkX > > >> 8ByFHVUGD0XU1PTKfCiw&m=z6ZZ_vt5XP--aKB5lpRRZxdVMA37hD_0ch7COCLdMt > > >> Lh > > >> Mve > > >> 8AJcbKfwRtBac267r&s=BQtj2lbWlu32mK0TP37XeZanal33QOf5HB1-33QJIqc&e > > >> = > > >>
