| From: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 17:08:24 |
| Message-ID: | 0DCFB765-B022-449E-9DE5-960F0EA076E9@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On May 15, 2018, at 9:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-15 17:20:05 | Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 |
| Previous Message | Tom Lane | 2018-05-15 16:54:05 | Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 |