Hi everyone, The SPDK compile job pulls from the LTS branch before every SPDK compile test. I have checked the local repository and it currently shows that it did pick up the commit 'a73286870ebf189629937515bd28714937f2498b: env_dpdk/pci: adapt to 20.11 EAL changes' Looking at the logs, I can see the changes have taken place. However, the error/warning messages are the same, and they highlight the lines that have already been changed. This issue persists after clearing the cache and rebuilding the container used to compile. Has anyone had an issue like this before? Thanks, Brandon On Wed, Nov 18, 2020 at 9:09 AM Lincoln Lavoie wrote: > Hi David, > > Let me check with Brandon. I believe it should pick it up, but I'm not > 100% sure. We generally don't track the downstream branches as closely > because the goal is testing DPDK patches with a "stable" system, i.e. not > having a patch on SDPK testing cause a failure on DPDK CI. > > Cheers, > Lincoln > > On Wed, Nov 18, 2020 at 4:32 AM David Marchand > wrote: > >> Hello, >> >> On Wed, Nov 18, 2020 at 9:36 AM Zawadzki, Tomasz >> wrote: >> > >> > Hi David, >> > >> > The change is now integrated into SPDK. Checking out branch v20.10.x >> will allow to resume SPDK job at UNH. >> >> Thanks Tomasz! >> >> Lincoln, >> Do you know when this change will be picked up by the UNH job? >> >> >> -- >> David Marchand >> >> > > -- > *Lincoln Lavoie* > Senior Engineer, Broadband Technologies > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > lylavoie@iol.unh.edu > https://www.iol.unh.edu > +1-603-674-2755 (m) > > -- Brandon Lo UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 blo@iol.unh.edu www.iol.unh.edu