DPDK patches and discussions
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: David Marchand <david.marchand@redhat.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	thomas@monjalon.net,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: |FAILURE| pw153190 [PATCH V3] Add new tracepoint function for type time_t
Date: Wed, 7 May 2025 10:21:26 +0800	[thread overview]
Message-ID: <e6ca8bfc-06dc-4844-9b2d-f44436050165@windriver.com> (raw)
In-Reply-To: <CAJFAV8zk=gzCagoU7c4=dsXcEFnLjiqrWxwTWANa-U77Uj=Taw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]


On 5/5/25 21:56, David Marchand wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hello,
>
> On Wed, Apr 30, 2025 at 7:21 AM Changqing Li<changqing.li@windriver.com>  wrote:
>> I'm new to this project, and have no clue about the failure,  could experts at this project provide
>>
>> some help about the following failure?
>>
>> + sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-30-AM-02-25-21
>>
>> Error: at line 2819: token "time_t": syntax error, unexpected IDENTIFIER
>> Error: Error creating AST
> I think this time_t type you added is not described in CTF.
> Have a look at 2114521cff91 ("trace: fix size_t field emitter").
>
> Copying the trace framework maintainers who will have a better idea.

Thanks David.

Copy the fail link here for easy access:

Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153190/

_github build: failed_
Build URL:https://github.com/ovsrobot/dpdk/actions/runs/14744930390

Regards

Changqing

>
>
> --
> David Marchand
>

[-- Attachment #2: Type: text/html, Size: 2332 bytes --]

  reply	other threads:[~2025-05-07  2:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29  3:00 [PATCH] " changqing.li
2025-04-29  3:04 ` [PATCH V2] " changqing.li
2025-04-30  1:34   ` [PATCH V3] " changqing.li
     [not found]     ` <20250430024403.2690306-1-robot@bytheb.org>
2025-04-30  5:21       ` |FAILURE| pw153190 " Changqing Li
2025-05-05 13:56         ` David Marchand
2025-05-07  2:21           ` Changqing Li [this message]
2025-05-08 13:53             ` [EXTERNAL] " Jerin Jacob

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=e6ca8bfc-06dc-4844-9b2d-f44436050165@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=skori@marvell.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).