On Tue, Dec 5, 2023 at 4:00 PM Eelco Chaudron wrote:
>
> When new drivers are introduced, the cache key is not accurately computed.
>
> Before the commit 1a1b3106d90e ("ci: Separate DPDK from OVS build."), the
> DPDK build process was integrated in .ci/linux-{setup,build}.sh scripts,
> where
On Tue, Dec 05, 2023 at 04:00:27PM +0100, Eelco Chaudron wrote:
> When new drivers are introduced, the cache key is not accurately computed.
>
> Before the commit 1a1b3106d90e ("ci: Separate DPDK from OVS build."), the
> DPDK build process was integrated in .ci/linux-{setup,build}.sh scripts,
>
On Tue, Dec 05, 2023 at 04:00:27PM +0100, Eelco Chaudron wrote:
> When new drivers are introduced, the cache key is not accurately computed.
>
> Before the commit 1a1b3106d90e ("ci: Separate DPDK from OVS build."), the
> DPDK build process was integrated in .ci/linux-{setup,build}.sh scripts,
>
When new drivers are introduced, the cache key is not accurately computed.
Before the commit 1a1b3106d90e ("ci: Separate DPDK from OVS build."), the
DPDK build process was integrated in .ci/linux-{setup,build}.sh scripts,
where specific lines were employed to generate the key. Since it is now
