automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: bruce.richardson@intel.com, robot@bytheb.org
Subject: |FAILURE| pw152489 [PATCH v4 11/11] member: use common AVX512 build support
Date: Wed, 19 Mar 2025 14:23:36 -0400	[thread overview]
Message-ID: <20250319182336.163621-1-robot@bytheb.org> (raw)
In-Reply-To: <20250319172942.2992053-12-bruce.richardson@intel.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/152489/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13953230965
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
102/104 DPDK:fast-tests / vdev_autotest                 OK              0.34s
103/104 DPDK:fast-tests / version_autotest              OK              0.34s
104/104 DPDK:fast-tests / telemetry_all                 OK              1.10s


Ok:                 97  
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            6   
Timeout:            0   

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-03-19-PM-06-21-23/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-03-19-PM-06-21-23
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
117/119 DPDK:fast-tests / vdev_autotest                  OK              0.24s
118/119 DPDK:fast-tests / version_autotest               OK              0.24s
119/119 DPDK:fast-tests / telemetry_all                  OK              1.06s


Ok:                 112 
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            6   
Timeout:            0   

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-03-19-PM-06-05-59/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-03-19-PM-06-05-59
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-03-19 18:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250319172942.2992053-12-bruce.richardson@intel.com>
2025-03-19 16:57 ` |SUCCESS| pw152479-152489 " qemudev
2025-03-19 17:02 ` qemudev
2025-03-19 17:32 ` |SUCCESS| pw152489 " checkpatch
2025-03-19 18:23 ` 0-day Robot [this message]
2025-03-19 20:16 ` |SUCCESS| pw152479-152489 [PATCH] [v4,11/11] member: use common AVX5 dpdklab
2025-03-19 20:21 ` dpdklab
2025-03-19 20:28 ` dpdklab
2025-03-19 20:29 ` dpdklab
2025-03-19 20:31 ` dpdklab
2025-03-19 20:34 ` dpdklab
2025-03-19 20:38 ` |PENDING| " dpdklab
2025-03-19 20:45 ` |SUCCESS| " dpdklab
2025-03-19 20:55 ` dpdklab
2025-03-19 20:57 ` dpdklab
2025-03-19 21:14 ` |FAILURE| " dpdklab
2025-03-19 21:22 ` |PENDING| " dpdklab
2025-03-19 21:44 ` |SUCCESS| " dpdklab
2025-03-19 21:48 ` dpdklab
2025-03-19 22:06 ` |FAILURE| " dpdklab
2025-03-19 22:10 ` |SUCCESS| " dpdklab
2025-03-19 22:12 ` dpdklab
2025-03-19 22:26 ` dpdklab
2025-03-19 23:13 ` dpdklab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250319182336.163621-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=bruce.richardson@intel.com \
    --cc=test-report@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).