[Bug 2063152] Re: [arm64] autopkgtest - some DPDK tests do not fit within CI memory constraints

Frode Nordahl 2063152 at bugs.launchpad.net
Thu May 2 08:28:51 UTC 2024


https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/o/openvswitch/20240501_021126_e862b@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/o/openvswitch/20240501_021215_8ac01@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/o/openvswitch/20240501_014114_7b2c4@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/o/openvswitch/20240501_014529_fcfa6@/log.gz

** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/2063152

Title:
  [arm64] autopkgtest - some DPDK tests do not fit within CI memory
  constraints

Status in openvswitch package in Ubuntu:
  Confirmed
Status in openvswitch source package in Mantic:
  Confirmed
Status in openvswitch source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]
  The autopkgtest for openvswitch on arm64 currently always fails, which prevents us from catching any real architecture specific regressions as dependencies are updated in the stable release.

  [ Test Plan ]
  Trigger autopkgtest runs against PPA and document their output / result.

  [ Regression Potential ]
  As this is a test-only change, I'd say none for the actual end user consumption of the package.

  For CI stability however, the issue appears to have been present
  throughout the development phase of Noble, so there may be test cases
  with architecture specific flakiness which has yet to be uncovered.
  Rest assured, we will follow up with any required updates if they do
  appear.

  [ Other Info ]
  There is an issue with running the DPDK tests on arm64 which is currently worked around by using 1G hugepages as opposed to 2M hugepages (bug 2059400) as well as increasing the number of pages available (bug 2063112).

  This workaround does however not work for the following tests:

      OVS-DPDK - MTU increase vport port
      OVS-DPDK - MTU decrease vport port
      OVS-DPDK - MTU upper bound vport port
      OVS-DPDK - user configured mempool

  I propose we skip the test until we find a more permanent solution to
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/2063152/+subscriptions




More information about the Ubuntu-openstack-bugs mailing list