Source: dpdk Version: 24.11.3-1 Severity: serious User: [email protected] Usertags: regression
Dear maintainer(s),Your package has an autopkgtest, great. However, I looked into the results as it showed up as a regression in stable-proposed and it fails most of the time now in testing. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The regression seems to roughly align with the deployment of our new host, which are more powerful, but have more tests in parallel. I suspect that just brought the test over the time limit in most cases (although we do the same on other architectures as well).
The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing.
More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html https://ci.debian.net/packages/d/dpdk/testing/arm64/64316857/ 091s Telemetry commands log:1091s ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― 1091s 84/84 DPDK:fast-tests / telemetry_all OK 1.05s
1091s 1091s 1091s Summary of Failures: 1091s1091s 51/84 DPDK:fast-tests / pflock_autotest TIMEOUT 120.15s killed by signal 15 SIGTERM 1091s 79/84 DPDK:fast-tests / ticketlock_autotest TIMEOUT 120.12s killed by signal 15 SIGTERM
1091s 1091s Ok: 80 1091s Fail: 0 1091s Skipped: 2 1091s Timeout: 2 1091s1091s Full log written to /tmp/autopkgtest-lxc.iw9952kp/downtmp/build.OuM/src/build/meson-logs/testlog.txt
1091s + ret=2 1091s + [ 2 -eq 125 ] 1091s + rm -rf /tmp/tmp.X2XzpNVyr5 1091s + exit 2
OpenPGP_signature.asc
Description: OpenPGP digital signature
