public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@seketeli.org>
To: "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org>
Subject: Re: [PATCH] ctf-reader: Assert on ir::hash_as_canonical_type_or_constant
Date: Tue, 21 Dec 2021 17:22:33 +0100	[thread overview]
Message-ID: <8735mm7ws6.fsf@seketeli.org> (raw)
In-Reply-To: <20211210025252.2309157-1-guillermo.e.martinez@oracle.com> (Guillermo E. Martinez via Libabigail's message of "Thu, 9 Dec 2021 20:52:52 -0600")

Hello Guillermo,

"Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org> a
écrit:

[...]

Thanks for the patch!

I have tested this patch and I've found some issues.  Please find my
comments below:

> diff --git a/tests/test-read-ctf.cc b/tests/test-read-ctf.cc
> index b448ddc5..7f5381f6 100644
> --- a/tests/test-read-ctf.cc
> +++ b/tests/test-read-ctf.cc
> @@ -220,6 +220,54 @@ static InOutSpec in_out_specs[] =
>      "data/test-read-ctf/PR27700/test-PR27700.abi",
>      "output/test-read-ctf/PR27700/test-PR27700.abi",
>    },
> +  {
> +    "data/test-read-ctf/test-callback.o",

This *.o is not present in the patch.  I think the remaining *.o
below are not present in the patch either.  So test/runtestreadctf
fails.

Also, you need to add these files to the tests/data/Makefile.am file.

As I've said elsewhere in the past, "make distcheck-fast" can help you
check if the files are really present in the tarball.

[...]

Cheers,

-- 
		Dodji

  reply	other threads:[~2021-12-21 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10  2:52 Guillermo E. Martinez
2021-12-21 16:22 ` Dodji Seketeli [this message]
2021-12-21 17:28   ` Guillermo Martinez
2021-12-21 19:29 ` [PATCH v2] " Guillermo E. Martinez
2022-01-03 14:48   ` Dodji Seketeli

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=8735mm7ws6.fsf@seketeli.org \
    --to=dodji@seketeli.org \
    --cc=libabigail@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).