automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mb@smartsharesystems.com, robot@bytheb.org
Subject: |FAILURE| pw144609 [RFC PATCH v11] mempool: fix mempool cache size
Date: Sat, 28 Sep 2024 14:23:52 -0400	[thread overview]
Message-ID: <20240928182352.3087627-1-robot@bytheb.org> (raw)
In-Reply-To: <20240928173244.1881152-1-mb@smartsharesystems.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11085833247
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
103/112 DPDK:fast-tests / telemetry_json_autotest  OK       0.27 s 
104/112 DPDK:fast-tests / thash_autotest        OK       0.27 s 
105/112 DPDK:fast-tests / threads_autotest      OK       0.32 s 
106/112 DPDK:fast-tests / ticketlock_autotest   OK       0.27 s 
107/112 DPDK:fast-tests / timer_autotest        OK       2.82 s 
108/112 DPDK:fast-tests / trace_autotest        OK       0.27 s 
109/112 DPDK:fast-tests / trace_autotest_with_traces  OK       0.27 s 
110/112 DPDK:fast-tests / vdev_autotest         OK       0.27 s 
111/112 DPDK:fast-tests / version_autotest      OK       0.27 s 
112/112 DPDK:fast-tests / telemetry_all         OK       1.07 s 

Ok:                   98
Expected Fail:         0
Fail:                  8
Unexpected Pass:       0
Skipped:               6
Timeout:               0

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
89/98 DPDK:fast-tests / telemetry_json_autotest  OK       0.37 s 
90/98 DPDK:fast-tests / thash_autotest        OK       0.37 s 
91/98 DPDK:fast-tests / threads_autotest      OK       0.42 s 
92/98 DPDK:fast-tests / ticketlock_autotest   OK       0.37 s 
93/98 DPDK:fast-tests / timer_autotest        OK       2.87 s 
94/98 DPDK:fast-tests / trace_autotest        OK       0.37 s 
95/98 DPDK:fast-tests / trace_autotest_with_traces  OK       0.37 s 
96/98 DPDK:fast-tests / vdev_autotest         OK       0.37 s 
97/98 DPDK:fast-tests / version_autotest      OK       0.37 s 
98/98 DPDK:fast-tests / telemetry_all         OK       1.12 s 

Ok:                   84
Expected Fail:         0
Fail:                  8
Unexpected Pass:       0
Skipped:               6
Timeout:               0

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2024-09-28 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240928173244.1881152-1-mb@smartsharesystems.com>
2024-09-28 17:06 ` |SUCCESS| " qemudev
2024-09-28 17:11 ` |FAILURE| " qemudev
2024-09-28 17:33 ` |SUCCESS| " checkpatch
2024-09-28 18:23 ` 0-day Robot [this message]

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=20240928182352.3087627-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=mb@smartsharesystems.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).