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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 9b67399691a67869446dd2bdcccd341280403f63
Date: Mon, 01 Jul 2024 04:58:14 -0700 (PDT)	[thread overview]
Message-ID: <668299d6.170a0220.7c634.0ba6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: 23.11-staging

9b67399691a67869446dd2bdcccd341280403f63 --> testing issues

Test environment and result as below:

+---------------------+--------------------+-------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_msvc_compile | dpdk_mingw64_compile |
+=====================+====================+===================+======================+
| Windows Server 2019 | PASS               | SKIPPED           | PASS                 |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 13.3        | FAIL               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| FreeBSD 14.1        | PASS               | SKIPPED           | SKIPPED              |
+---------------------+--------------------+-------------------+----------------------+
| Windows Server 2022 | PASS               | PASS              | PEND                 |
+---------------------+--------------------+-------------------+----------------------+

==== 20 line log output for FreeBSD 13.3 (dpdk_meson_compile): ====
|                  ^
../lib/log/rte_log.h:333:4: note: expanded from macro 'RTE_LOGTYPE_'
../lib/eal/unix/eal_firmware.c:45:3: error: pasting formed 'RTE_LOGTYPE_"could not initialise libarchive for zstd compression"', an invalid preprocessing token
45 |                 RTE_LOG(DEBUG, "could not initialise libarchive for zstd compression");
|                 ^
../lib/log/rte_log.h:333:17: note: expanded from macro 'RTE_LOG'
333 |                  RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
|                               ^
../lib/eal/unix/eal_firmware.c:45:3: error: use of undeclared identifier 'RTE_LOGTYPE_'
../lib/log/rte_log.h:333:4: note: expanded from macro 'RTE_LOG'
333 |                  RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
|                  ^
../lib/log/rte_log.h:333:4: note: expanded from macro 'RTE_LOGTYPE_'
4 errors generated.
[62/1810] Generating lib/telemetry.sym_chk with a custom command (wrapped by meson to capture output)
[63/1810] Generating lib/log.sym_chk with a custom command (wrapped by meson to capture output)
[64/1810] Compiling C object lib/librte_eal.a.p/eal_freebsd_eal_lcore.c.o
[65/1810] Compiling C object lib/librte_eal.a.p/eal_freebsd_eal_hugepage_info.c.o
[66/1810] Compiling C object lib/librte_eal.a.p/eal_freebsd_eal_interrupts.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29657/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-01 11:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 11:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-01 14:16 dpdklab
2024-07-01 13:42 dpdklab
2024-07-01 13:34 dpdklab
2024-07-01 13:27 dpdklab
2024-07-01 13:24 dpdklab
2024-07-01 13:20 dpdklab
2024-07-01 13:17 dpdklab
2024-07-01 13:11 dpdklab
2024-07-01 13:10 dpdklab
2024-07-01 13:07 dpdklab
2024-07-01 13:02 dpdklab
2024-07-01 13:00 dpdklab
2024-07-01 12:56 dpdklab
2024-07-01 12:54 dpdklab
2024-07-01 12:54 dpdklab
2024-07-01 12:54 dpdklab
2024-07-01 12:50 dpdklab
2024-07-01 12:37 dpdklab
2024-07-01 12:04 dpdklab
2024-07-01 11:57 dpdklab
2024-07-01 11:55 dpdklab
2024-07-01 11:53 dpdklab
2024-07-01 11:49 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=668299d6.170a0220.7c634.0ba6SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).