Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Date
Msg-id 0DCFB765-B022-449E-9DE5-960F0EA076E9@gmail.com
Whole thread Raw
In response to Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On May 15, 2018, at 9:54 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Mark Dilger <hornschnorter@gmail.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?

I mostly develop on mac and linux and don't look at the windows system
too much:


Windows Server 2008 R2 Standard
Service Pack 1
Processor: Intel Xeon CPU E5-2676 v3 @ 2.40GHz
Installed memory:  8.00 GB
System type: 64 bit Operating System

Microsoft Visual Studio 2008 Beta2 x64 cross tools
Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Next
From: Tom Lane
Date:
Subject: Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11