On 3/11/20 5:57 AM, Yanqin Wei wrote: > Hi Ilya, > > This patch has been in the review pipeline for some time. It runs stable on > our internal repo more than two months. > Could you give us some suggestion about the next action I can take to speed > up the merge of this patch?
Hi. Sorry for things taking so long. I have this patch in my backlog for this or next week. The main concern right know is possible significant increase of the checking time. Are you sure that we need all the listed jobs? Do you expect some arm64 specific issues on the linking stage? I mean, maybe we could reduce number of different combinations of "shared" flags. I had no chance to run this, so I don't know how much time these jobs really takes and what is the total time difference. Best regards, Ilya Maximets. > > Best Regards, > Wei Yanqin > >> -----Original Message----- >> From: Lance Yang <[email protected]> >> Sent: Tuesday, January 21, 2020 9:06 AM >> To: Ilya Maximets <[email protected]>; [email protected] >> Cc: [email protected]; Yanqin Wei <[email protected]>; [email protected]; >> Gavin Hu <[email protected]>; Ruifeng Wang <[email protected]>; >> Jieqiang Wang <[email protected]>; Malvika Gupta >> <[email protected]>; nd <[email protected]> >> Subject: RE: [ovs-dev] [PATCH v2 3/3] travis: Enable OvS Travis CI for arm >> >> >>> -----Original Message----- >>> From: Ilya Maximets <[email protected]> >>> Sent: Saturday, December 7, 2019 12:39 AM >>> To: Lance Yang (Arm Technology China) <[email protected]>; ovs- >>> [email protected] >>> Cc: [email protected]; [email protected]; Yanqin Wei (Arm Technology China) >>> <[email protected]>; [email protected]; Gavin Hu (Arm Technology >>> China) <[email protected]>; Ruifeng Wang (Arm Technology China) >>> <[email protected]>; Jieqiang Wang (Arm Technology China) >>> <[email protected]>; Malvika Gupta <[email protected]>; nd >>> <[email protected]> >>> Subject: Re: [ovs-dev] [PATCH v2 3/3] travis: Enable OvS Travis CI for >>> arm >>> >>> On 06.12.2019 04:26, Lance Yang wrote: >>>> Enable part of travis jobs with gcc compiler for arm64 architecture >>>> >>>> 1. Add arm jobs into the matrix in .travis.yml configuration file 2. >>>> To enable OVS-DPDK jobs, set the build target according to different >>>> CPU architectures 3. Temporarily disable sparse checker because of >>>> static code checking failure on arm64 >>>> >>>> Successful travis build jobs report: >>>> https://travis-ci.org/yzyuestc/ovs/builds/621037339 >>>> >>>> Reviewed-by: Yanqin Wei <[email protected]> >>>> Reviewed-by: Jieqiang Wang <[email protected]> >>>> Reviewed-by: Gavin Hu <[email protected]> >>>> Signed-off-by: Lance Yang <[email protected]> >>>> --- >>> >>> Compiler crashed while building DPDK: >>> >>> /home/travis/build/ovsrobot/ovs/dpdk-dir/drivers/net/ixgbe/ixgbe_pf.c: >>> In function >>> ‘ixgbe_pf_host_configure’: >>> /home/travis/build/ovsrobot/ovs/dpdk-dir/drivers/net/ixgbe/ixgbe_pf.c: >>> 297:1: internal compiler error: Segmentation fault >>> >>> https://travis-ci.org/ovsrobot/ovs/jobs/621434216#L1999 >>> >>> This is not good. >>> Need to check how frequently this happens. >>> >>> Best regards, Ilya Maximets. >> [Lance] >> Hi Ilya, >> >> After you give us the feedback about the segmentation fault issue, we keep >> running the travis CI to observe the frequency. We run those arm jobs on a >> regular basis and clear cache on every single build. We have run the build at >> least 2 times a day for more than a month. >> >> The good thing is that we haven't reproduce the segfault issue. Job reports >> are >> available at: https://travis-ci.org/yzyuestc/ovs/builds/639064033 >> >> Travis CI community also made some adjustment on their side, you can see >> their reply here: https://travis-ci.community/t/segfaults-in-arm64- >> environment/5617/13 >> >> I think the segfault issue may occur by chance. At least, it is not a >> frequent one, >> which is unlikely to cause issues to OVS developers. Could you please check >> it >> again? >> >> Best Regards, >> Lance > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
