automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: rjarry@redhat.com, robot@bytheb.org
Subject: |FAILURE| pw154285 [RFC PATCH dpdk] fib6: implement RCU rule reclamation
Date: Tue, 10 Jun 2025 12:04:47 -0400	[thread overview]
Message-ID: <20250610160447.393919-1-robot@bytheb.org> (raw)
In-Reply-To: <20250610145341.38271-2-rjarry@redhat.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15563237596
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"ubuntu-22.04-gcc-abi+debug+doc+examples+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
####################################################################################
103/105 DPDK:fast-tests / vdev_autotest                 OK              0.34s
104/105 DPDK:fast-tests / version_autotest              OK              0.34s
105/105 DPDK:fast-tests / telemetry_all                 OK              1.14s


Ok:                 98  
Expected Fail:      0   
Fail:               1   
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
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-10-PM-03-46-55/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-10-PM-03-46-55
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
118/120 DPDK:fast-tests / vdev_autotest                  OK              0.23s
119/120 DPDK:fast-tests / version_autotest               OK              0.23s
120/120 DPDK:fast-tests / telemetry_all                  OK              1.32s


Ok:                 113 
Expected Fail:      0   
Fail:               1   
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
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-10-PM-04-01-39/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-06-10-PM-04-01-39
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-06-10 16:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250610145341.38271-2-rjarry@redhat.com>
2025-06-10 14:25 ` |SUCCESS| " qemudev
2025-06-10 14:29 ` |FAILURE| " qemudev
2025-06-10 14:54 ` |WARNING| " checkpatch
2025-06-10 16:04 ` 0-day Robot [this message]
2025-06-10 18:04 ` |SUCCESS| pw154285 [PATCH] [RFC] fib6: implement RCU rule reclamatio dpdklab
2025-06-10 18:06 ` dpdklab
2025-06-10 18:21 ` dpdklab
2025-06-10 18:36 ` |PENDING| " dpdklab
2025-06-10 18:54 ` |WARNING| " dpdklab
2025-06-10 19:02 ` dpdklab
2025-06-10 19:23 ` |SUCCESS| " dpdklab
2025-06-10 19:28 ` |WARNING| " dpdklab
2025-06-10 20:25 ` |FAILURE| " dpdklab
2025-06-10 20:29 ` |SUCCESS| " dpdklab
2025-06-10 20:29 ` dpdklab
2025-06-10 20:59 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 22:12 ` |FAILURE| " dpdklab
2025-06-11  2:24 ` |PENDING| " dpdklab
2025-06-11  2:28 ` |WARNING| " dpdklab
2025-06-11  2:29 ` dpdklab
2025-06-11  2:29 ` dpdklab
2025-06-11  2:30 ` dpdklab
2025-06-11  2:30 ` dpdklab
2025-06-11  2:31 ` dpdklab
2025-06-11  2:32 ` dpdklab
2025-06-11  4:10 ` |SUCCESS| " dpdklab
2025-06-11  6:49 ` |FAILURE| " dpdklab
2025-06-11  8:47 ` |SUCCESS| " dpdklab
2025-06-11  8:49 ` |FAILURE| " 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=20250610160447.393919-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=rjarry@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).