Re: Question for coverage report

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Steven Niu <niushiji(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Question for coverage report
Date: 2025-10-21 18:26:06
Message-ID: CAOYmi+=REXfz+=9L0MdtCatkXtRkuXr+v1w8=81M2esZNQZsHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 17, 2025 at 2:15 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> Hmm, these reports are supposed to have been generated with -O0. This
> is the configure line:
>
> ./configure --cache-file=/home/coverage/pgsrc/configure.cache --enable-depend --enable-coverage --enable-tap-tests --enable-nls --with-python --with-perl --with-tcl --with-openssl --with-libxml --with-ldap --with-pam --with-llvm --with-lz4 --enable-injection-points CFLAGS=-O0 'CPPFLAGS=-DCOPY_PARSE_PLAN_TREES -DWRITE_READ_PARSE_PLAN_TREES -DRAW_EXPRESSION_COVERAGE_TEST' LLVM_CONFIG=/usr/bin/llvm-config-19 CLANG=clang-19 >> $LOG 2>&1
>
> Is this somehow not effective?

Are you able to double-check the compiler invocation for pgoutput.c?

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2025-10-21 18:26:30 Re: Skip unregistered custom kinds on stats load
Previous Message Philip Alger 2025-10-21 17:53:34 Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement