Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Dilger <hornschnorter(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Hao Lee <mixtrue(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Date: 2018-05-15 16:54:05
Message-ID: 25837.1526403245@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Dilger <hornschnorter(at)gmail(dot)com> writes:
> I'm curious why the Windows build farm members did not pick this up. Or
> perhaps they did? (I don't get emails about that.)

They did not, and I too was wondering why not.

> If none of the animals
> are configured to detect this bug, perhaps the community needs another
> Windows animal configured along the lines of the build machine I am using?

+1. How do you have yours configured, anyway?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2018-05-15 17:08:24 Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Previous Message Mark Dilger 2018-05-15 16:39:23 Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11