automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	David Marchand <david.marchand@redhat.com>
Subject: |FAILURE| pw130330-130331 [PATCH] [v2,2/2] devtools: list symbols by
Date: Tue, 15 Aug 2023 07:32:00 -0700 (PDT)	[thread overview]
Message-ID: <64db8c60.0c0a0220.d3ff2.2f58SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130331

_Testing issues_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, August 15 2023 10:36:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:68150b90bda5e8f81ad1b1bad82be653b1d42a81

130330-130331 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+

==== 20 line log output for FreeBSD 13 (dpdk_meson_compile): ====

[82/1779] Generating lib/rcu.sym_chk with a custom command (wrapped by meson to capture output)
FAILED: lib/rcu.sym_chk
/usr/local/bin/meson --internal exe --capture lib/rcu.sym_chk -- /usr/home/jenkins/jenkins-agent/workspace/Generic-VM-DPDK-Compile-Meson/dpdk/buildtools/check-symbols.sh /usr/home/jenkins/jenkins-agent/workspace/Generic-VM-DPDK-Compile-Meson/dpdk/lib/rcu/version.map lib/librte_rcu.a
--- stderr ---
awk: illegal primary in regular expression ^\t[a-zA-Z_0-9]*;(| # WINDOWS_NO_EXPORT)$ at  # WINDOWS_NO_EXPORT)$
source line number 6
context is
/^\t[a-zA-Z_0-9]*;(| # >>>  WINDOWS_NO_EXPORT)$/ <<<

[83/1779] Generating lib/eal.sym_chk with a custom command (wrapped by meson to capture output)
FAILED: lib/eal.sym_chk
/usr/local/bin/meson --internal exe --capture lib/eal.sym_chk -- /usr/home/jenkins/jenkins-agent/workspace/Generic-VM-DPDK-Compile-Meson/dpdk/buildtools/check-symbols.sh /usr/home/jenkins/jenkins-agent/workspace/Generic-VM-DPDK-Compile-Meson/dpdk/lib/eal/version.map lib/librte_eal.a
--- stderr ---
awk: illegal primary in regular expression ^\t[a-zA-Z_0-9]*;(| # WINDOWS_NO_EXPORT)$ at  # WINDOWS_NO_EXPORT)$
source line number 6
context is
/^\t[a-zA-Z_0-9]*;(| # >>>  WINDOWS_NO_EXPORT)$/ <<<

ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27341/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-08-15 14:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 14:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 15:28 dpdklab
2023-08-15 15:27 dpdklab
2023-08-15 15:24 dpdklab
2023-08-15 15:23 dpdklab
2023-08-15 15:21 dpdklab
2023-08-15 15:18 dpdklab
2023-08-15 15:17 dpdklab
2023-08-15 15:13 dpdklab
2023-08-15 15:09 dpdklab
2023-08-15 15:07 dpdklab
2023-08-15 14:58 dpdklab
2023-08-15 14:58 dpdklab
2023-08-15 14:57 dpdklab
2023-08-15 14:55 dpdklab
2023-08-15 14:55 dpdklab
2023-08-15 14:54 dpdklab
2023-08-15 14:52 dpdklab
2023-08-15 14:51 dpdklab
2023-08-15 14:47 dpdklab
2023-08-15 14:47 dpdklab
2023-08-15 14:23 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=64db8c60.0c0a0220.d3ff2.2f58SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).