automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw138282 [RFC] eal: add rte_counted_by attribute
Date: Tue, 12 Mar 2024 18:03:26 -0400	[thread overview]
Message-ID: <20240312220326.3746173-1-robot@bytheb.org> (raw)
In-Reply-To: <20240312210308.8788-1-stephen@networkplumber.org>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8255939306
Build Logs:
-----------------------Summary of failed steps-----------------------
"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-clang-asan+doc+tests" at step Build and test
####################################################################################
88/97 DPDK:fast-tests / telemetry_json_autotest  FAIL     0.03 s (killed by signal 11 SIGSEGV)
89/97 DPDK:fast-tests / thash_autotest        OK       0.37 s 
90/97 DPDK:fast-tests / threads_autotest      OK       0.47 s 
91/97 DPDK:fast-tests / ticketlock_autotest   FAIL     0.03 s (killed by signal 11 SIGSEGV)
92/97 DPDK:fast-tests / timer_autotest        FAIL     0.03 s (killed by signal 11 SIGSEGV)
93/97 DPDK:fast-tests / trace_autotest        FAIL     0.03 s (killed by signal 11 SIGSEGV)
94/97 DPDK:fast-tests / trace_autotest_with_traces  FAIL     0.03 s (killed by signal 11 SIGSEGV)
95/97 DPDK:fast-tests / vdev_autotest         FAIL     0.03 s (killed by signal 11 SIGSEGV)
96/97 DPDK:fast-tests / version_autotest      OK       0.37 s 
97/97 DPDK:fast-tests / telemetry_all         FAIL     1.07 s (exit status 139 or signal 11 SIGSEGV)

Ok:                   61
Expected Fail:         0
Fail:                 33
Unexpected Pass:       0
Skipped:               3
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-03-12 22:03 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312210308.8788-1-stephen@networkplumber.org>
2024-03-12 20:39 ` |SUCCESS| " qemudev
2024-03-12 20:44 ` qemudev
2024-03-12 21:04 ` |WARNING| " checkpatch
2024-03-12 22:00 ` |SUCCESS| pw138282 [PATCH] " dpdklab
2024-03-12 22:02 ` dpdklab
2024-03-12 22:03 ` dpdklab
2024-03-12 22:03 ` dpdklab
2024-03-12 22:03 ` 0-day Robot [this message]
2024-03-12 22:03 ` dpdklab
2024-03-12 22:06 ` dpdklab
2024-03-12 22:21 ` dpdklab
2024-03-12 22:21 ` dpdklab
2024-03-12 22:22 ` dpdklab
2024-03-12 22:22 ` dpdklab
2024-03-12 22:23 ` dpdklab
2024-03-12 22:23 ` dpdklab
2024-03-12 22:23 ` dpdklab
2024-03-12 22:24 ` dpdklab
2024-03-12 22:24 ` dpdklab
2024-03-12 22:25 ` dpdklab
2024-03-12 22:26 ` dpdklab
2024-03-12 22:28 ` dpdklab
2024-03-12 22:35 ` dpdklab
2024-03-12 22:35 ` dpdklab
2024-03-12 22:37 ` dpdklab
2024-03-12 22:38 ` dpdklab
2024-03-12 22:38 ` dpdklab
2024-03-12 22:38 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-12 22:39 ` dpdklab
2024-03-12 22:40 ` dpdklab
2024-03-12 22:40 ` dpdklab
2024-03-12 22:40 ` dpdklab
2024-03-12 22:40 ` dpdklab
2024-03-12 22:41 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:42 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:43 ` dpdklab
2024-03-12 22:44 ` dpdklab
2024-03-12 22:44 ` dpdklab
2024-03-12 22:44 ` dpdklab
2024-03-12 22:51 ` dpdklab
2024-03-12 22:52 ` dpdklab
2024-03-12 22:52 ` dpdklab
2024-03-12 22:52 ` dpdklab
2024-03-12 22:53 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:58 ` dpdklab
2024-03-12 22:59 ` dpdklab
2024-03-12 22:59 ` dpdklab
2024-03-12 22:59 ` dpdklab
2024-03-12 23:00 ` dpdklab
2024-03-12 23:00 ` dpdklab
2024-03-12 23:01 ` dpdklab
2024-03-12 23:01 ` dpdklab
2024-03-12 23:01 ` dpdklab
2024-03-12 23:02 ` dpdklab
2024-03-12 23:02 ` dpdklab
2024-03-12 23:03 ` dpdklab
2024-03-12 23:04 ` dpdklab
2024-03-12 23:05 ` dpdklab
2024-03-12 23:08 ` dpdklab
2024-03-12 23:10 ` dpdklab
2024-03-12 23:13 ` dpdklab
2024-03-12 23:39 ` dpdklab
2024-03-12 23:57 ` dpdklab
2024-03-13  0:00 ` dpdklab
2024-03-13  0:09 ` dpdklab
2024-03-13  0:12 ` dpdklab
2024-03-13  0:50 ` dpdklab
2024-03-16 12:27 ` dpdklab
2024-03-16 13:03 ` 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=20240312220326.3746173-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).