Re: What is happening on buildfarm member crake?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: What is happening on buildfarm member crake?
Date: 2014-01-20 00:53:19
Message-ID: 52DC737F.7030900@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 01/19/2014 04:14 PM, Tom Lane wrote:
> I wrote:
>> I don't think any other buildfarm critters are showing this either,
> Scratch that --- closer inspection of the buildfarm logs shows that
> kouprey and lapwing have suffered identical failures, though much less
> often than crake. That lets out the theory that it's x86_64 specific, or
> even 64-bit specific. Still have no idea why I can't reproduce it here.

I can give you an account on the machine if you want to play.

Also crake does produce backtraces on core dumps, and they are at the
bottom of the buildfarm log. The latest failure backtrace is reproduced
below.

================== stack trace: /home/bf/bfr/root/HEAD/inst/data-C/core.12584 ==================
[New LWP 12584]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `postgres: buildfarm contrib_regression_test_shm_mq'.
Program terminated with signal 11, Segmentation fault.
#0 SetLatch (latch=0x1c) at pg_latch.c:509
509 if (latch->is_set)
#0 SetLatch (latch=0x1c) at pg_latch.c:509
#1 0x000000000064c04e in procsignal_sigusr1_handler (postgres_signal_arg=<optimized out>) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/storage/ipc/procsignal.c:289
#2 <signal handler called>
#3 _dl_fini () at dl-fini.c:190
#4 0x000000361ba39931 in __run_exit_handlers (status=0, listp=0x361bdb1668, run_list_atexit=true) at exit.c:78
#5 0x000000361ba399b5 in __GI_exit (status=<optimized out>) at exit.c:100
#6 0x00000000006485a6 in proc_exit (code=0) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/storage/ipc/ipc.c:143
#7 0x0000000000663abb in PostgresMain (argc=<optimized out>, argv=<optimized out>, dbname=0x12b8170 "contrib_regression_test_shm_mq", username=<optimized out>) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/tcop/postgres.c:4225
#8 0x000000000062220f in BackendRun (port=0x12d6bf0) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/postmaster/postmaster.c:4083
#9 BackendStartup (port=0x12d6bf0) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/postmaster/postmaster.c:3772
#10 ServerLoop () at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/postmaster/postmaster.c:1583
#11 PostmasterMain (argc=<optimized out>, argv=<optimized out>) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/postmaster/postmaster.c:1238
#12 0x000000000045e2e8 in main (argc=3, argv=0x12b7430) at /home/bf/bfr/root/HEAD/pgsql.25562/../pgsql/src/backend/main/main.c:205

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-01-20 01:22:42 Re: What is happening on buildfarm member crake?
Previous Message Maor Lipchuk 2014-01-20 00:32:57 Re: Add value to error message when size extends