| From: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add Dockerfile for OSS Scanner |
| Date: | 2026-10-17 18:09:55 |
| Message-ID: | CAH7T-apYF141q7kYY1Bu5pjd8g6oo2JotSaMtWz2gx8B4OGhuw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 17, 2026 at 12:39 PM Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> On Sat, Oct 17, 2026 at 11:58:20AM -0400, Andres Freund wrote:
> >
> > Can't we just use the actual container used for CI for that?
>
> I had not realized it was that easy. Attached.
Yes, using that CI image is nicer.
v2 builds with tools/check fine for me on the same box with the
expected aio test failures.
I did have one random other failure but it's not really the image.
From subscription/023_twophase_stream:
2026-10-17 17:44:48.950 UTC startup[49516] FATAL: could not
resize shared memory segment "/PostgreSQL.3189924516" to 1048576
bytes: No space left on device
Docker's default /dev/shm is 64 MB which ends up being too small for
meson's default parallelism (nproc, so 16 on my test box). Running it
with --shm-size=1g or default size with MESON_TESTTHREADS=4 fixes it.
I think this is the type of thing an agent like Claude would figure out
automatically and retry. But might want to add it to a comment so it
knows about it in advance.
Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manu | 2026-10-17 18:54:04 | Re: ANSI SQL proposal: SELECT DISTINCT ON (... ORDER BY ...) and UNION DISTINCT ON (... ORDER BY ...) |
| Previous Message | Mihail Nikalayeu | 2026-10-17 17:57:00 | Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements |