From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: andremue@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw153487 [PATCH 2/2] test/strsep: add tests for function strsep()
Date: Fri, 16 May 2025 10:44:30 -0400 [thread overview]
Message-ID: <20250516144430.659601-1-robot@bytheb.org> (raw)
In-Reply-To: <1747401734-6303-2-git-send-email-andremue@linux.microsoft.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153487/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15069945476
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
####################################################################################
103/105 DPDK:fast-tests / vdev_autotest OK 0.33s
104/105 DPDK:fast-tests / version_autotest OK 0.33s
105/105 DPDK:fast-tests / telemetry_all OK 1.10s
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-05-16-PM-02-23-54/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-05-16-PM-02-23-54
+ 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
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-05-16 14:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1747401734-6303-2-git-send-email-andremue@linux.microsoft.com>
2025-05-16 12:49 ` |SUCCESS| pw153486-153487 " qemudev
2025-05-16 12:53 ` qemudev
2025-05-16 13:22 ` |SUCCESS| pw153487 [PATCH 2/2] test/strsep: add tests for function strsep checkpatch
2025-05-16 14:44 ` 0-day Robot [this message]
2025-05-16 17:33 ` |SUCCESS| pw153486-153487 [PATCH] [2/2] test/strsep: add tests for f dpdklab
2025-05-16 17:45 ` |PENDING| " dpdklab
2025-05-16 17:47 ` |SUCCESS| " dpdklab
2025-05-16 17:48 ` dpdklab
2025-05-16 17:48 ` dpdklab
2025-05-16 17:48 ` dpdklab
2025-05-16 17:51 ` dpdklab
2025-05-16 17:52 ` |PENDING| " dpdklab
2025-05-16 18:00 ` dpdklab
2025-05-16 18:02 ` |SUCCESS| " dpdklab
2025-05-16 18:07 ` |PENDING| " dpdklab
2025-05-16 18:22 ` |SUCCESS| " dpdklab
2025-05-16 18:26 ` dpdklab
2025-05-16 18:48 ` dpdklab
2025-05-16 18:49 ` dpdklab
2025-05-16 18:54 ` dpdklab
2025-05-16 18:57 ` dpdklab
2025-05-16 21:07 ` dpdklab
2025-05-17 0:07 ` 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=20250516144430.659601-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=andremue@linux.microsoft.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).