automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: andremue@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw151611 [PATCH v2 5/5] mbuf: enable to be compiled with MSVC
Date: Tue, 18 Feb 2025 21:43:50 -0500	[thread overview]
Message-ID: <20250219024350.3833844-1-robot@bytheb.org> (raw)
In-Reply-To: <1739929198-28432-6-git-send-email-andremue@linux.microsoft.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13403919518
Build Logs:
-----------------------Summary of failed steps-----------------------
"Check patches" failed at step Check patches
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "Check patches" at step Check patches
####################################################################################
  REF_GIT_REPO: https://dpdk.org/git/dpdk
  REF_GIT_TAG: v24.11
##[endgroup]
+ git remote add upstream https://dpdk.org/git/dpdk
+ git fetch upstream main
From https://dpdk.org/git/dpdk
 * branch                  main       -> FETCH_HEAD
 * [new branch]            main       -> upstream/main
+ failed=
+ devtools/check-doc-vs-code.sh upstream/main
+ devtools/check-meson.py
+ devtools/check-symbol-maps.sh
Found only in symbol map file:
	lib/net/version_ms_linker.map: rte_net_crc_calc=rte_net_crc_calc_v26
	lib/net/version_ms_linker.map: rte_net_crc_set_alg=rte_net_crc_set_alg_v26
	lib/net/version_ms_linker.map: rte_net_crc_calc=rte_net_crc_calc_v26
	lib/net/version_ms_linker.map: rte_net_crc_set_alg=rte_net_crc_set_alg_v26
Found badly formatted maps:
	rte_net_crc_calc=rte_net_crc_calc_v26;
	rte_net_crc_set_alg=rte_net_crc_set_alg_v26;
	rte_net_crc_calc=rte_net_crc_calc_v26;
	rte_net_crc_set_alg=rte_net_crc_set_alg_v26;
+ failed=true
+ '[' -z true ']'
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "Check patches" at step Check patches
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-02-19  2:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1739929198-28432-6-git-send-email-andremue@linux.microsoft.com>
2025-02-19  1:07 ` |SUCCESS| pw151607-151611 " qemudev
2025-02-19  1:11 ` qemudev
2025-02-19  1:41 ` |SUCCESS| pw151611 " checkpatch
2025-02-19  2:16 ` |SUCCESS| pw151607-151611 [PATCH] [v2,5/5] mbuf: enable to be compil dpdklab
2025-02-19  2:27 ` dpdklab
2025-02-19  2:43 ` 0-day Robot [this message]
2025-02-19  2:45 ` dpdklab
2025-02-19  2:48 ` dpdklab
2025-02-19  2:52 ` dpdklab
2025-02-19  2:55 ` dpdklab
2025-02-19  3:22 ` dpdklab
2025-02-19  3:39 ` dpdklab
2025-02-19  3:46 ` dpdklab
2025-02-19 12:53 ` 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=20250219024350.3833844-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=andremue@linux.microsoft.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).