Re: test_json_parser/002_inline is kind of slow

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: test_json_parser/002_inline is kind of slow
Date: 2025-11-03 17:57:18
Message-ID: CAOYmi+=1Ha+JYkxu4mjcCepGrGiW5d6rKYgjsTSqfdPemW-rTQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 2, 2025 at 4:34 AM Mihail Nikalayeu
<mihailnikalayeu(at)gmail(dot)com> wrote:
> Not sure it is related, but probably yes - got weird CI [0] issue on
> BSD (patch itself does not change anything may affect that):

Thank you for the report!

> [19:24:12.744](0.000s) not ok 1802 - unescaped control: stderr has
> correct number of entries
> [19:24:12.744](0.000s) # Failed test 'unescaped control: stderr has
> correct number of entries'
> # at /home/postgres/postgres/src/test/modules/test_json_parser/t/002_inline.pl
> line 151.
> [19:24:12.756](0.012s) # got: '0'
> # expected: '13'

More missing stderr on NetBSD.

As luck would have it, I've been working on updating IPC::Run in the
CI [1], which should hopefully fix this? (And if it doesn't, at least
we won't be chasing a fixed bug.) Andres just recently gave me a
recipe to try to unblock my work on that, and I will bump up the
priority.

--Jacob

[1] https://postgr.es/m/CAOYmi%2BkvZDVLndQ8M2wr5k5wYYVoKF87B3ZOnY37ABQDA0a5GA%40mail.gmail.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-11-03 17:59:45 Re: psql --help=variables missing csv_fieldsep
Previous Message Sami Imseih 2025-11-03 17:50:48 Re: Improve LWLock tranche name visibility across backends