From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: changqing.li@windriver.com, robot@bytheb.org
Subject: |FAILURE| pw153181 [PATCH] Add new tracepoint function for type time_t
Date: Tue, 29 Apr 2025 00:04:06 -0400 [thread overview]
Message-ID: <20250429040406.2014855-1-robot@bytheb.org> (raw)
In-Reply-To: <20250429030017.1126516-1-changqing.li@windriver.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153181/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14722667991
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+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-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ 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-04-29-AM-03-44-49/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49
[error] at line 2819: token "time_t": syntax error, unexpected IDENTIFIER
[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49".
[warning] [Context] Cannot open_trace of format ctf at path /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49.
[warning] [Context] cannot open trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49" from /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49 for reading.
[error] Cannot open any trace for reading.
[error] opening trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-44-49" for reading.
[error] none of the specified trace paths could be opened.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ 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-04-29-AM-03-59-37/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37
[error] at line 2819: token "time_t": syntax error, unexpected IDENTIFIER
[error] Error creating AST
[warning] Unable to open trace metadata for path "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37".
[warning] [Context] Cannot open_trace of format ctf at path /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37.
[warning] [Context] cannot open trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37" from /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37 for reading.
[error] Cannot open any trace for reading.
[error] opening trace "/home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-29-AM-03-59-37" for reading.
[error] none of the specified trace paths could be opened.
##[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-04-29 4:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250429030017.1126516-1-changqing.li@windriver.com>
2025-04-29 2:27 ` |SUCCESS| " qemudev
2025-04-29 2:31 ` qemudev
2025-04-29 3:00 ` |WARNING| " checkpatch
2025-04-29 3:26 ` |SUCCESS| pw153181 [PATCH] Add new tracepoint function for type time dpdklab
2025-04-29 3:30 ` dpdklab
2025-04-29 3:43 ` |PENDING| " dpdklab
2025-04-29 3:45 ` |SUCCESS| " dpdklab
2025-04-29 3:47 ` dpdklab
2025-04-29 3:48 ` |PENDING| " dpdklab
2025-04-29 3:50 ` |SUCCESS| " dpdklab
2025-04-29 3:52 ` |PENDING| " dpdklab
2025-04-29 3:55 ` |SUCCESS| " dpdklab
2025-04-29 4:01 ` dpdklab
2025-04-29 4:04 ` 0-day Robot [this message]
2025-04-29 4:07 ` |PENDING| " dpdklab
2025-04-29 4:10 ` |SUCCESS| " dpdklab
2025-04-29 4:11 ` |PENDING| " dpdklab
2025-04-29 4:34 ` |SUCCESS| " dpdklab
2025-04-29 4:59 ` dpdklab
2025-04-29 5:01 ` dpdklab
2025-04-29 5:34 ` dpdklab
2025-04-29 6:55 ` dpdklab
2025-04-29 8:18 ` 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=20250429040406.2014855-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=changqing.li@windriver.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).