automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: nicolas.chautru@intel.com, robot@bytheb.org
Subject: |FAILURE| pw150428 [PATCH v1 3/3] baseband/acc: add internal logging
Date: Thu, 23 Jan 2025 16:44:21 -0500	[thread overview]
Message-ID: <20250123214421.4043610-1-robot@bytheb.org> (raw)
In-Reply-To: <20250123202807.2089618-4-nicolas.chautru@intel.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12938045224
Build Logs:
-----------------------Summary of failed steps-----------------------
"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-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
+ target=build/examples/dpdk-vhost_blk
+ target=vhost_blk
+ [ -e examples/vhost_blk/Makefile ]
+ echo vhost_blk
+ continue
+ read target
+ target=build/examples/dpdk-l2fwd-event
+ target=l2fwd-event
+ [ -e examples/l2fwd-event/Makefile ]
+ echo l2fwd-event
+ continue
+ read target
+ make -C install/usr/local/share/dpdk/examples/bbdev_app clean shared
make: Entering directory '/home/runner/work/dpdk/dpdk/install/usr/local/share/dpdk/examples/bbdev_app'
rm -f build/bbdev build/bbdev-static build/bbdev-shared
test -d build && rmdir -p build || true
ccache gcc -O3 -include rte_config.h -march=corei7 -mrtm -I/home/runner/work/dpdk/dpdk/install/usr/local/include -I/usr/lib/include -I/usr/lib/include/libnl3 -I/usr/lib/include -DALLOW_EXPERIMENTAL_API main.c -o build/bbdev-shared  -L/home/runner/work/dpdk/dpdk/install/usr/local/lib -L/usr/lib/lib/x86_64-linux-gnu -Wl,--as-needed -lrte_node -lrte_graph -lrte_pipeline -lrte_table -lrte_pdump -lrte_port -lrte_fib -lrte_pdcp -lrte_ipsec -lrte_vhost -lrte_stack -lrte_security -lrte_sched -lrte_reorder -lrte_rib -lrte_mldev -lrte_regexdev -lrte_rawdev -lrte_power -lrte_pcapng -lrte_member -lrte_lpm -lrte_latencystats -lrte_jobstats -lrte_ip_frag -lrte_gso -lrte_gro -lrte_gpudev -lrte_dispatcher -lrte_eventdev -lrte_efd -lrte_dmadev -lrte_distributor -lrte_cryptodev -lrte_compressdev -lrte_cfgfile -lrte_bpf -lrte_bitratestats -lrte_bbdev -lrte_acl -lrte_timer -lrte_hash -lrte_metrics -lrte_cmdline -lrte_pci -lrte_ethdev -lrte_meter -lrte_net -lrte_mbuf -lrte_mempool -lrte_rcu -lrte_ring -lrte_eal -lrte_telemetry -lrte_argparse -lrte_kvargs -lrte_log -lbsd
In file included from main.c:35:
/home/runner/work/dpdk/dpdk/install/usr/local/include/rte_bbdev.h:36:10: fatal error: bbdev_trace.h: No such file or directory
   36 | #include "bbdev_trace.h"
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:40: build/bbdev-shared] Error 1
make: Leaving directory '/home/runner/work/dpdk/dpdk/install/usr/local/share/dpdk/examples/bbdev_app'
##[error]Process completed with exit code 2.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-01-23 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250123202807.2089618-4-nicolas.chautru@intel.com>
2025-01-23 20:07 ` |SUCCESS| pw150426-150428 " qemudev
2025-01-23 20:11 ` qemudev
2025-01-23 20:40 ` |SUCCESS| pw150428 " checkpatch
2025-01-23 21:18 ` |PENDING| pw150426-150428 [PATCH] [v1,3/3] baseband/acc: add interna dpdklab
2025-01-23 21:21 ` dpdklab
2025-01-23 21:21 ` dpdklab
2025-01-23 21:22 ` dpdklab
2025-01-23 21:24 ` |SUCCESS| " dpdklab
2025-01-23 21:28 ` |PENDING| " dpdklab
2025-01-23 21:33 ` |SUCCESS| " dpdklab
2025-01-23 21:36 ` dpdklab
2025-01-23 21:36 ` |WARNING| " dpdklab
2025-01-23 21:38 ` |SUCCESS| " dpdklab
2025-01-23 21:44 ` 0-day Robot [this message]
2025-01-23 21:48 ` dpdklab
2025-01-23 21:51 ` dpdklab
2025-01-23 22:07 ` dpdklab
2025-01-23 22:09 ` dpdklab
2025-01-23 22:51 ` |WARNING| " dpdklab
2025-01-23 22:52 ` dpdklab
2025-01-23 22:56 ` |SUCCESS| " 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=20250123214421.4043610-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=nicolas.chautru@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).