DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinj@marvell.com>
To: Changqing Li <changqing.li@windriver.com>,
	David Marchand <david.marchand@redhat.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] Re: |FAILURE| pw153190 [PATCH V3] Add new tracepoint function for type time_t
Date: Thu, 8 May 2025 13:53:33 +0000	[thread overview]
Message-ID: <BY3PR18MB47853116D8C07076A91BAC3CC88BA@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <e6ca8bfc-06dc-4844-9b2d-f44436050165@windriver.com>

> 		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.



time_t is not defined in CTF spec. See https://diamon.org/ctf/v1.8.3/#specification.
You can create new type using typealias with integer or structure as backend type. See meta_data_type_emit() in DPDK code base where we created new types.



      reply	other threads:[~2025-05-08 13:53 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
2025-05-08 13:53             ` Jerin Jacob [this message]

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=BY3PR18MB47853116D8C07076A91BAC3CC88BA@BY3PR18MB4785.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=changqing.li@windriver.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).