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
Subject: |WARNING| pw144487 [PATCH] [RFC,v10] mempool: fix mempool cache size
Date: Thu, 26 Sep 2024 20:06:41 -0700 (PDT)	[thread overview]
Message-ID: <66f62141.d40a0220.29ec99.26efSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240926205323.1747234-1-mb@smartsharesystems.com>

Test-Label: iol-compile-amd64-testing
Test-Status: WARNING
http://dpdk.org/patch/144487

_Testing issues_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Thursday, September 26 2024 20:53:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144487 --> testing issues

Upstream job id: Windows-Compile-DPDK-VS#3225

Test environment and result as below:

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

==== 20 line log output for Windows Server 2022 (dpdk_mingw64_compile): ====
In function 'rte_mempool_do_generic_get',
inlined from 'rte_mempool_generic_get' at ..\lib\mempool/rte_mempool.h:1695:8,
inlined from 'rte_mempool_get_bulk' at ..\lib\mempool/rte_mempool.h:1730:9,
inlined from '__rte_crypto_op_raw_bulk_alloc' at ..\lib\cryptodev/rte_crypto.h:291:6,
inlined from 'rte_crypto_op_bulk_alloc' at ..\lib\cryptodev/rte_crypto.h:344:6,
inlined from 'test_queue_pair_descriptor_count' at ../app/test/test_cryptodev.c:2462:2:
..\lib\mempool/rte_mempool.h:1645:38: error: array subscript 4095 is above array bounds of 'void *[1024]' [-Werror=array-bounds=]
1645 |                         cache_objs = &cache->objs[cache->len];
|                                      ^~~~~~~~~~~~~~~~~~~~~~~~
..\lib\mempool/rte_mempool.h: In function 'test_queue_pair_descriptor_count':
..\lib\mempool/rte_mempool.h:111:44: note: while referencing 'objs'
111 |         alignas(RTE_CACHE_LINE_SIZE) void *objs[RTE_MEMPOOL_CACHE_MAX_SIZE * 2];
|                                            ^~~~
cc1.exe: all warnings being treated as errors
[629/762] Compiling C object app/dpdk-test.exe.p/test_test_fib.c.obj
[630/762] Compiling C object app/dpdk-test.exe.p/test_test_func_reentrancy.c.obj
[631/762] Compiling C object app/dpdk-test.exe.p/test_test_hash_functions.c.obj
[632/762] Compiling C object app/dpdk-test.exe.p/test_test_fib_perf.c.obj
[633/762] Compiling C object app/dpdk-test.exe.p/test_test_hash.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-27  3:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240926205323.1747234-1-mb@smartsharesystems.com>
2024-09-26 20:26 ` |SUCCESS| pw144487 [RFC PATCH v10] " qemudev
2024-09-26 20:31 ` |FAILURE| " qemudev
2024-09-26 20:54 ` |SUCCESS| " checkpatch
2024-09-26 21:43 ` |FAILURE| " 0-day Robot
2024-09-27  2:35 ` |SUCCESS| pw144487 [PATCH] [RFC,v10] " dpdklab
2024-09-27  2:39 ` dpdklab
2024-09-27  2:40 ` dpdklab
2024-09-27  2:44 ` |WARNING| " dpdklab
2024-09-27  2:46 ` |SUCCESS| " dpdklab
2024-09-27  2:50 ` |PENDING| " dpdklab
2024-09-27  2:50 ` |SUCCESS| " dpdklab
2024-09-27  3:06 ` dpdklab [this message]
2024-09-27  3:10 ` |WARNING| " dpdklab
2024-09-27  3:13 ` |FAILURE| " dpdklab
2024-09-27  3:26 ` |PENDING| " dpdklab
2024-09-27  3:28 ` |SUCCESS| " dpdklab
2024-09-27  3:39 ` |FAILURE| " dpdklab
2024-09-27  3:52 ` |PENDING| " dpdklab
2024-09-27  4:06 ` |FAILURE| " dpdklab
2024-09-27  4:08 ` dpdklab
2024-09-27  4:12 ` dpdklab
2024-09-27  4:12 ` dpdklab
2024-09-27  4:14 ` |SUCCESS| " dpdklab
2024-09-27  4:31 ` |WARNING| " dpdklab
2024-09-27  6:27 ` |FAILURE| " dpdklab
2024-09-27  8: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=66f62141.d40a0220.29ec99.26efSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).