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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw131231-131232 [PATCH] [v2,2/2] random: make rte_rand() t
Date: Thu, 07 Sep 2023 21:46:38 -0700 (PDT)	[thread overview]
Message-ID: <64faa72e.170a0220.10dca.ae99SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, September 07 2023 15:24:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e92ba1426914db1d224dd5e9a1743657681b8814

131231-131232 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
[154/798] Compiling C object lib/librte_eal.a.p/eal_common_rte_malloc.c.obj
[155/798] Compiling C object lib/librte_eal.a.p/eal_common_rte_random.c.obj
FAILED: lib/librte_eal.a.p/eal_common_rte_random.c.obj
"clang" "-Ilib\librte_eal.a.p" "-Ilib" "-I..\lib" "-I." "-I.." "-Iconfig" "-I..\config" "-Ilib\eal\include" "-I..\lib\eal\include" "-Ilib\eal\windows\include" "-I..\lib\eal\windows\include" "-Ilib\eal\x86\include" "-I..\lib\eal\x86\include" "-Ilib\eal\common" "-I..\lib\eal\common" "-Ilib\eal" "-I..\lib\eal" "-Ilib\log" "-I..\lib\log" "-Ilib\kvargs" "-I..\lib\kvargs" "-IC:\Program Files\Mellanox\MLNX_WinOF2_DevX_SDK\inc" "-Xclang" "-fcolor-diagnostics" "-pipe" "-D_FILE_OFFSET_BITS=64" "-Wall" "-Winvalid-pch" "-Wextra" "-Werror" "-std=c11" "-O3" "-include" "rte_config.h" "-Wcast-qual" "-Wdeprecated" "-Wformat" "-Wformat-nonliteral" "-Wformat-security" "-Wmissing-declarations" "-Wmissing-prototypes" "-Wnested-externs" "-Wold-style-definition" "-Wpointer-arith" "-Wsign-compare" "-Wstrict-prototypes" "-Wundef" "-Wwrite-strings" "-Wno-address-of-packed-member" "-Wno-missing-field-initializers" "-D_GNU_SOURCE" "-D_WIN32_WINNT=0x0A00" "-D_CRT_SECURE_NO_WARNINGS" "-march=native" "-mrtm" "-DAL
 LOW_EXPERIMENTAL_API" "-DALLOW_INTERNAL_API" "-DABI_VERSION=\"24.0\"" "-DRTE_LOG_DEFAULT_LOGTYPE=lib.eal" "-DRTE_ANNOTATE_LOCKS" "-Wthread-safety" -MD -MQ lib/librte_eal.a.p/eal_common_rte_random.c.obj -MF "lib\librte_eal.a.p\eal_common_rte_random.c.obj.d" -o lib/librte_eal.a.p/eal_common_rte_random.c.obj "-c" ../lib/eal/common/rte_random.c
../lib/eal/common/rte_random.c:136:10: error: mutex 'rte_rand_lock' is not held on every path through here [-Werror,-Wthread-safety-analysis]
return &rand_states[idx];
^
../lib/eal/common/rte_random.c:133:3: note: mutex acquired here
rte_spinlock_lock(&rte_rand_lock);
^
../lib/eal/common/rte_random.c:143:3: error: releasing mutex 'rte_rand_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_spinlock_unlock(&rte_rand_lock);
^
2 errors generated.
[156/798] Generating symbol file lib/rte_kvargs-24.dll.p/rte_kvargs-24.dll.symbols
[157/798] Compiling C object lib/librte_eal.a.p/eal_windows_eal.c.obj
[158/798] Generating symbol file lib/rte_telemetry-24.dll.p/rte_telemetry-24.dll.symbols
[159/798] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_memzone.c.obj
[160/798] Compiling C object lib/librte_eal.a.p/eal_common_eal_common_options.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-08  4:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  4:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-08  6:15 dpdklab
2023-09-08  6:10 dpdklab
2023-09-08  6:06 dpdklab
2023-09-08  6:04 dpdklab
2023-09-08  6:00 dpdklab
2023-09-08  5:59 dpdklab
2023-09-08  5:57 dpdklab
2023-09-08  5:52 dpdklab
2023-09-08  5:51 dpdklab
2023-09-08  5:51 dpdklab
2023-09-08  5:41 dpdklab
2023-09-08  5:38 dpdklab
2023-09-08  5:37 dpdklab
2023-09-08  5:36 dpdklab
2023-09-08  5:35 dpdklab
2023-09-08  5:34 dpdklab
2023-09-08  5:33 dpdklab
2023-09-08  5:32 dpdklab
2023-09-08  5:31 dpdklab
2023-09-08  5:30 dpdklab
2023-09-08  5:28 dpdklab
2023-09-08  5:27 dpdklab
2023-09-08  5:27 dpdklab
2023-09-08  5:25 dpdklab
2023-09-08  5:25 dpdklab
2023-09-08  4:58 dpdklab
2023-09-08  4:50 dpdklab
2023-09-08  4:49 dpdklab
2023-09-08  4:49 dpdklab
2023-09-08  4:49 dpdklab
2023-09-08  4:49 dpdklab
2023-09-08  4:46 dpdklab
2023-09-08  4:45 dpdklab
2023-09-08  4:45 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=64faa72e.170a0220.10dca.ae99SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).