Re: Why is parula failing?

On Tue, 2 Apr 2024 at 15:01, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Tharakan, Robins" <tharar@amazon.com> writes:
> > So although HEAD ran fine, but I saw multiple failures (v12, v13, v16) all of which passed on subsequent-tries,
> > of which some were even"signal 6: Aborted".
>
> Ugh...


parula didn't send any reports to buildfarm for the past 44 hours. Logged in
to see that postgres was stuck on pg_sleep(), which was quite odd! I captured
the backtrace and triggered another run on HEAD, which came out
okay.

I'll keep an eye on this instance more often for the next few days.
(Let me know if I could capture more if a run gets stuck again)


(gdb) bt
#0  0x0000ffff952ae954 in epoll_pwait () from /lib64/libc.so.6
#1  0x000000000083e9c8 in WaitEventSetWaitBlock (nevents=1, occurred_events=<optimized out>, cur_timeout=297992, set=0x2816dac0) at latch.c:1570
#2  WaitEventSetWait (set=0x2816dac0, timeout=timeout@entry=600000, occurred_events=occurred_events@entry=0xffffc395ed28, nevents=nevents@entry=1, wait_event_info=wait_event_info@entry=150994946) at latch.c:1516
#3  0x000000000083ed84 in WaitLatch (latch=<optimized out>, wakeEvents=wakeEvents@entry=41, timeout=600000, wait_event_info=wait_event_info@entry=150994946) at latch.c:538
#4  0x0000000000907404 in pg_sleep (fcinfo=<optimized out>) at misc.c:406
#5  0x0000000000696b10 in ExecInterpExpr (state=0x28384040, econtext=0x28383e38, isnull=<optimized out>) at execExprInterp.c:764
#6  0x00000000006ceef8 in ExecEvalExprSwitchContext (isNull=0xffffc395ee9f, econtext=0x28383e38, state=<optimized out>) at ../../../src/include/executor/executor.h:356
#7  ExecProject (projInfo=<optimized out>) at ../../../src/include/executor/executor.h:390
#8  ExecResult (pstate=<optimized out>) at nodeResult.c:135
#9  0x00000000006b7aec in ExecProcNode (node=0x28383d28) at ../../../src/include/executor/executor.h:274
#10 gather_getnext (gatherstate=0x28383b38) at nodeGather.c:287
#11 ExecGather (pstate=0x28383b38) at nodeGather.c:222
#12 0x000000000069aa4c in ExecProcNode (node=0x28383b38) at ../../../src/include/executor/executor.h:274
#13 ExecutePlan (execute_once=<optimized out>, dest=0x2831ffb0, direction=<optimized out>, numberTuples=0, sendTuples=<optimized out>, operation=CMD_SELECT, use_parallel_mode=<optimized out>, planstate=0x28383b38, estate=0x28383910) at execMain.c:1646
#14 standard_ExecutorRun (queryDesc=0x283239c0, direction=<optimized out>, count=0, execute_once=<optimized out>) at execMain.c:363
#15 0x000000000086d454 in PortalRunSelect (portal=portal@entry=0x281f0fb0, forward=forward@entry=true, count=0, count@entry=9223372036854775807, dest=dest@entry=0x2831ffb0) at pquery.c:924
#16 0x000000000086ec70 in PortalRun (portal=portal@entry=0x281f0fb0, count=count@entry=9223372036854775807, isTopLevel=isTopLevel@entry=true, run_once=run_once@entry=true, dest=dest@entry=0x2831ffb0, altdest=altdest@entry=0x2831ffb0, qc=qc@entry=0xffffc395f250) at pquery.c:768
#17 0x000000000086a944 in exec_simple_query (query_string=query_string@entry=0x28171c90 "SELECT pg_sleep(0.1);") at postgres.c:1274
#18 0x000000000086b480 in PostgresMain (dbname=<optimized out>, username=<optimized out>) at postgres.c:4680
#19 0x0000000000866a0c in BackendMain (startup_data=<optimized out>, startup_data_len=<optimized out>) at backend_startup.c:101
#20 0x00000000007c1738 in postmaster_child_launch (child_type=child_type@entry=B_BACKEND, startup_data=startup_data@entry=0xffffc395f718 "", startup_data_len=startup_data_len@entry=4, client_sock=client_sock@entry=0xffffc395f720) at launch_backend.c:265
#21 0x00000000007c5120 in BackendStartup (client_sock=0xffffc395f720) at postmaster.c:3593
#22 ServerLoop () at postmaster.c:1674
#23 0x00000000007c6dc8 in PostmasterMain (argc=argc@entry=8, argv=argv@entry=0x2816d320) at postmaster.c:1372
#24 0x0000000000496bb8 in main (argc=8, argv=0x2816d320) at main.c:197
 
 
>
> The update_personality.pl script in the buildfarm client distro
> is what to use to adjust OS version or compiler version data.
>
Thanks. Fixed that.

-
robins