automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: david.marchand@redhat.com, robot@bytheb.org
Subject: |FAILURE| pw138100 [PATCH] test/lcores: reduce cpu consumption
Date: Thu,  7 Mar 2024 07:24:08 -0500	[thread overview]
Message-ID: <20240307122408.2037666-1-robot@bytheb.org> (raw)
In-Reply-To: <20240307113324.845309-1-david.marchand@redhat.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8187558685
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-static-mingw" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
[683/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_dmadev.c.obj'.
[684/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_fib.c.obj'.
[685/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ethdev_api.c.obj'.
[686/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_fib6_perf.c.obj'.
[687/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ethdev_link.c.obj'.
[688/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_hash_functions.c.obj'.
[689/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_hash_multiwriter.c.obj'.
[690/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_hash.c.obj'.
[691/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_func_reentrancy.c.obj'.
[692/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_lcores.c.obj'.
FAILED: app/a172ced@@dpdk-test@exe/test_test_lcores.c.obj 
ccache x86_64-w64-mingw32-gcc -Iapp/a172ced@@dpdk-test@exe -Iapp -I../app -Ilib/cmdline -I../lib/cmdline -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 -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Idrivers/net/ring -I../drivers/net/ring -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/windows -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/argparse -I../lib/argparse -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/metrics -I../lib/metrics -Ilib/bitratestats -I../lib/bitratestats -Ilib/cryptodev -I../lib/cryptodev -Ilib/security -I../lib/security -Ilib/dmadev -I../lib/dmadev -Ilib/fib -I../lib/fib -Ilib/rib -I../lib/rib -Ilib/lpm -I../lib/lpm -Ilib/ip_frag -I../lib/ip_frag -Ilib/latencystats -I../lib/latencystats -Ilib/pcapng -I../lib/pcapng -Ilib/reorder -I../lib/reorder -Ilib/stack -I../lib/stack -Ilib/timer -I../lib/timer -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -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-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -D_WIN32_WINNT=0x0A00 -D__USE_MINGW_ANSI_STDIO -march=native -mrtm -DALLOW_EXPERIMENTAL_API -Wno-format-truncation -fno-strict-aliasing -DALLOW_INTERNAL_API -MD -MQ 'app/a172ced@@dpdk-test@exe/test_test_lcores.c.obj' -MF 'app/a172ced@@dpdk-test@exe/test_test_lcores.c.obj.d' -o 'app/a172ced@@dpdk-test@exe/test_test_lcores.c.obj' -c ../app/test/test_lcores.c
../app/test/test_lcores.c: In function ‘thread_loop’:
../app/test/test_lcores.c:47:3: error: implicit declaration of function ‘sched_yield’ [-Werror=implicit-function-declaration]
   47 |   sched_yield();
      |   ^~~~~~~~~~~
../app/test/test_lcores.c:47:3: error: nested extern declaration of ‘sched_yield’ [-Werror=nested-externs]
cc1: all warnings being treated as errors
[693/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_fib_perf.c.obj'.
[694/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_logs.c.obj'.
[695/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_ipfrag.c.obj'.
[696/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_hash_readwrite_lf_perf.c.obj'.
[697/1454] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cryptodev.c.obj'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-03-07 12:24 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307113324.845309-1-david.marchand@redhat.com>
2024-03-07 11:09 ` |SUCCESS| " qemudev
2024-03-07 11:14 ` qemudev
2024-03-07 11:34 ` checkpatch
2024-03-07 12:24 ` 0-day Robot [this message]
2024-03-07 12:51 ` dpdklab
2024-03-07 13:02 ` dpdklab
2024-03-07 13:03 ` dpdklab
2024-03-07 13:07 ` dpdklab
2024-03-07 13:12 ` dpdklab
2024-03-07 13:12 ` dpdklab
2024-03-07 13:21 ` dpdklab
2024-03-07 13:35 ` dpdklab
2024-03-07 13:36 ` dpdklab
2024-03-07 13:44 ` dpdklab
2024-03-07 13:44 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:47 ` dpdklab
2024-03-07 13:47 ` dpdklab
2024-03-07 13:48 ` dpdklab
2024-03-07 13:48 ` dpdklab
2024-03-07 14:07 ` |FAILURE| " dpdklab
2024-03-07 14:08 ` dpdklab
2024-03-07 14:09 ` |SUCCESS| " dpdklab
2024-03-07 14:11 ` |FAILURE| " dpdklab
2024-03-07 14:12 ` dpdklab
2024-03-07 14:12 ` |SUCCESS| " dpdklab
2024-03-07 14:12 ` dpdklab
2024-03-07 14:13 ` dpdklab
2024-03-07 14:13 ` dpdklab
2024-03-07 14:13 ` |FAILURE| " dpdklab
2024-03-07 14:14 ` |SUCCESS| " dpdklab
2024-03-07 14:14 ` |FAILURE| " dpdklab
2024-03-07 14:15 ` dpdklab
2024-03-07 14:18 ` dpdklab
2024-03-07 14:19 ` dpdklab
2024-03-07 14:20 ` |SUCCESS| " dpdklab
2024-03-07 14:20 ` |FAILURE| " dpdklab
2024-03-07 14:20 ` |SUCCESS| " dpdklab
2024-03-07 14:20 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:22 ` dpdklab
2024-03-07 14:22 ` dpdklab
2024-03-07 14:29 ` dpdklab
2024-03-07 14:29 ` dpdklab
2024-03-07 14:30 ` dpdklab
2024-03-07 14:31 ` dpdklab
2024-03-07 14:32 ` dpdklab
2024-03-07 14:32 ` dpdklab
2024-03-07 14:33 ` dpdklab
2024-03-07 14:33 ` |FAILURE| " dpdklab
2024-03-07 14:34 ` dpdklab
2024-03-07 14:34 ` |SUCCESS| " dpdklab
2024-03-07 14:34 ` dpdklab
2024-03-07 14:35 ` dpdklab
2024-03-07 14:35 ` |FAILURE| " dpdklab
2024-03-07 14:36 ` |SUCCESS| " dpdklab
2024-03-07 14:37 ` dpdklab
2024-03-07 14:38 ` dpdklab
2024-03-07 14:40 ` dpdklab
2024-03-07 14:48 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 14:51 ` dpdklab
2024-03-07 15:24 ` dpdklab
2024-03-07 16:44 ` |FAILURE| " dpdklab
2024-03-07 21:05 ` |SUCCESS| " dpdklab
2024-03-08  5:26 ` dpdklab
2024-03-08  5:27 ` dpdklab
2024-03-08  5:32 ` dpdklab
2024-03-08  5:32 ` dpdklab
2024-03-11 20:00 ` dpdklab
2024-03-11 20:36 ` 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=20240307122408.2037666-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=david.marchand@redhat.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).