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| pw144954 [PATCH v2] service: fix deadlock on worker lcore exit
Date: Thu,  3 Oct 2024 03:45:12 -0400	[thread overview]
Message-ID: <20241003074512.3795448-1-robot@bytheb.org> (raw)
In-Reply-To: <20241003065702.3051158-1-david.marchand@redhat.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11157452626
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-debug+doc+examples+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.83 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:                  105
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
+ [ 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
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-10-03  7:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241003065702.3051158-1-david.marchand@redhat.com>
2024-10-03  6:37 ` |SUCCESS| " qemudev
2024-10-03  6:41 ` |FAILURE| " qemudev
2024-10-03  6:58 ` |SUCCESS| " checkpatch
2024-10-03  7:45 ` 0-day Robot [this message]
2024-10-03  8:18 ` |SUCCESS| pw144954 [PATCH] [v2] service: fix deadlock on worker lcor dpdklab
2024-10-03  8:19 ` dpdklab
2024-10-03  8:23 ` dpdklab
2024-10-03  8:25 ` dpdklab
2024-10-03  8:28 ` dpdklab
2024-10-03  8:30 ` dpdklab
2024-10-03  8:32 ` dpdklab
2024-10-03  8:34 ` dpdklab
2024-10-03  8:47 ` dpdklab
2024-10-03  8:56 ` dpdklab
2024-10-03 10:03 ` dpdklab
2024-10-03 10:12 ` |PENDING| " dpdklab
2024-10-03 10:42 ` dpdklab
2024-10-03 10:51 ` |FAILURE| " dpdklab
2024-10-03 10:52 ` dpdklab
2024-10-03 11:00 ` dpdklab
2024-10-03 11:00 ` dpdklab
2024-10-03 11:03 ` dpdklab
2024-10-03 11:08 ` dpdklab
2024-10-03 12:15 ` dpdklab
2024-10-03 12:17 ` dpdklab
2024-10-03 12:19 ` dpdklab
2024-10-03 12:23 ` dpdklab
2024-10-03 12:25 ` |SUCCESS| " dpdklab
2024-10-03 12:31 ` |FAILURE| " dpdklab
2024-10-03 12:33 ` dpdklab
2024-10-03 12:34 ` dpdklab
2024-10-03 12:37 ` |SUCCESS| " dpdklab
2024-10-03 12:40 ` |FAILURE| " dpdklab
2024-10-03 12:43 ` dpdklab
2024-10-03 12:44 ` dpdklab
2024-10-03 12:46 ` dpdklab
2024-10-03 12:48 ` dpdklab
2024-10-03 12:52 ` dpdklab
2024-10-03 12:54 ` dpdklab
2024-10-03 12:55 ` dpdklab
2024-10-03 13:01 ` 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=20241003074512.3795448-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).