recent deadlock regression test failures

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: recent deadlock regression test failures
Date: 2017-04-07 16:57:49
Message-ID: 20170407165749.pstcakbc637opkax@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

There's two machines that recently report changes in deadlock detector
output:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hyrax&dt=2017-04-05%2018%3A58%3A04
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=friarbird&dt=2017-04-07%2004%3A20%3A01

both just failed twice in a row:
https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=hyrax&br=HEAD
https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=friarbird&br=HEAD
without previous errors of the same ilk.

I don't think any recent changes are supposed to affect deadlock
detector behaviour?

- Andres

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2017-04-07 16:58:07 pgbench --progress-timestamp no longer works correctly
Previous Message Andres Freund 2017-04-07 16:49:35 valgrind errors around dsa.c