automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: david.marchand@redhat.com, robot@bytheb.org
Subject: |FAILURE| pw152267 [RFC v2 2/2] build: generate symbol maps
Date: Thu,  6 Mar 2025 09:06:43 -0500	[thread overview]
Message-ID: <20250306140643.1369363-1-robot@bytheb.org> (raw)
In-Reply-To: <20250306125021.2231121-2-david.marchand@redhat.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13699360862
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-static-mingw" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
	crypto/mvsam:	not supported on Windows
	crypto/nitrox:	only supported on Linux
	crypto/null:	not supported on Windows
	crypto/octeontx:	only supported on 64-bit Linux
	crypto/openssl:	not supported on Windows
	crypto/scheduler:	not supported on Windows
	crypto/uadk:	only supported on Linux
	crypto/virtio:	not supported on Windows
	regex/*:	missing internal dependency, "regexdev"
	ml/cnxk:	only supported on 64-bit Linux
	gpu/cuda:	only supported on Linux
	power/*:	missing internal dependency, "power"
	

Message: DPDK build config complete:
  source path = "/home/runner/work/dpdk/dpdk"
  build path  = "/home/runner/work/dpdk/dpdk/build"
Build targets in project: 217

Option buildtype is: debugoptimized [default: release]
Found ninja-1.10.1 at /usr/bin/ninja
+ ninja -C build
ninja: Entering directory `build'
ninja: error: '/home/runner/work/dpdk/dpdk/lib/net/version.map', needed by 'lib/rte_net_mingw.map', missing and no known rule to make it
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-03-06 14:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250306125021.2231121-2-david.marchand@redhat.com>
2025-03-06 12:20 ` |SUCCESS| pw152266-152267 " qemudev
2025-03-06 12:25 ` qemudev
2025-03-06 13:17 ` |SUCCESS| pw152266-152267 [PATCH] [RFC,v2,2/2] build: generate symbo dpdklab
2025-03-06 13:24 ` dpdklab
2025-03-06 13:27 ` dpdklab
2025-03-06 13:30 ` |PENDING| " dpdklab
2025-03-06 13:34 ` |FAILURE| " dpdklab
2025-03-06 13:34 ` |PENDING| " dpdklab
2025-03-06 13:35 ` |FAILURE| " dpdklab
2025-03-06 13:36 ` |SUCCESS| " dpdklab
2025-03-06 13:39 ` dpdklab
2025-03-06 13:41 ` |FAILURE| " dpdklab
2025-03-06 13:41 ` |PENDING| " dpdklab
2025-03-06 13:42 ` dpdklab
2025-03-06 13:45 ` |FAILURE| " dpdklab
2025-03-06 13:48 ` |SUCCESS| " dpdklab
2025-03-06 13:50 ` dpdklab
2025-03-06 13:50 ` |FAILURE| " dpdklab
2025-03-06 13:53 ` dpdklab
2025-03-06 13:54 ` |SUCCESS| " dpdklab
2025-03-06 14:02 ` |FAILURE| " dpdklab
2025-03-06 14:03 ` dpdklab
2025-03-06 14:03 ` dpdklab
2025-03-06 14:03 ` dpdklab
2025-03-06 14:05 ` |SUCCESS| " dpdklab
2025-03-06 14:06 ` 0-day Robot [this message]
2025-03-06 14:08 ` |FAILURE| " dpdklab
2025-03-06 14:20 ` dpdklab
2025-03-06 14:33 ` |SUCCESS| " dpdklab
2025-03-06 14:37 ` |FAILURE| " dpdklab
2025-03-06 15:09 ` |SUCCESS| " dpdklab
2025-03-06 15:47 ` dpdklab
2025-03-06 16:20 ` 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=20250306140643.1369363-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=david.marchand@redhat.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).