Thread: Searching for: Fast windows buildfarm animal

Hi,

It's common that half the buildfarm has reported back before a single
windows buildfarm animal reports. And if they report a failure one often
has to wait for hours for the next run.

It'd be awesome if somebody could set up a windows animal that runs
frequently (i.e. checks for build needed every minute or five) and is
fast enough to not take ages to finish a build.

Perhaps some recipient has that, or knows somebody with the necessary
hardware / resources available?

Greetings,

Andres Freund

Greetings,

* Andres Freund (andres@anarazel.de) wrote:
> It's common that half the buildfarm has reported back before a single
> windows buildfarm animal reports. And if they report a failure one often
> has to wait for hours for the next run.

Yes, that's been rather annoying.

> It'd be awesome if somebody could set up a windows animal that runs
> frequently (i.e. checks for build needed every minute or five) and is
> fast enough to not take ages to finish a build.

Done.

'dory' was approved today which checks for new commits every 5 minutes
and, as an added bonus, builds with a somewhat more recent version of
Visual Studio (2015) and a recent Windows Server version (2016) as
compared to the other Windows systems.  While it's still not quite as
fast as our faster buildfarm animals, it's at least able to report in
within 20-30 minutes or so, as compared to hours.

We'll probably continue to tweak the system a bit, but it's at least up
and running now for HEAD, REL_10 and REL9_6 (older branches don't work
easily with VS2015, as discussed elsewhere).

If anyone has any specific questions about it or suggestions, please
feel free to reach out.

Thanks!

Stephen

Stephen Frost <sfrost@snowman.net> writes:
> * Andres Freund (andres@anarazel.de) wrote:
>> It'd be awesome if somebody could set up a windows animal that runs
>> frequently (i.e. checks for build needed every minute or five) and is
>> fast enough to not take ages to finish a build.

> Done.

Thanks!

BTW, dory just fell over in HEAD:

*** c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/test/regress/expected/partition_prune.out    Fri Apr 20 16:03:09
2018
--- c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/test/regress/results/partition_prune.out    Fri Apr 20 20:12:43
2018
***************
*** 1778,1788 ****
  -- Execute query 5 times to allow choose_custom_plan
  -- to start considering a generic plan.
  execute ab_q4 (1, 8);
!  avg
! -----
!
! (1 row)
!
  execute ab_q4 (1, 8);
   avg
  -----
--- 1778,1784 ----
  -- Execute query 5 times to allow choose_custom_plan
  -- to start considering a generic plan.
  execute ab_q4 (1, 8);
! ERROR:  lost connection to parallel worker
  execute ab_q4 (1, 8);
   avg
  -----

Wonder how reproducible that will be.

            regards, tom lane

On 04/20/2018 07:55 PM, Stephen Frost wrote:
> Greetings,
>
> * Andres Freund (andres@anarazel.de) wrote:
>> It's common that half the buildfarm has reported back before a single
>> windows buildfarm animal reports. And if they report a failure one often
>> has to wait for hours for the next run.
> Yes, that's been rather annoying.
>
>> It'd be awesome if somebody could set up a windows animal that runs
>> frequently (i.e. checks for build needed every minute or five) and is
>> fast enough to not take ages to finish a build.
> Done.
>
> 'dory' was approved today which checks for new commits every 5 minutes
> and, as an added bonus, builds with a somewhat more recent version of
> Visual Studio (2015) and a recent Windows Server version (2016) as
> compared to the other Windows systems.  While it's still not quite as
> fast as our faster buildfarm animals, it's at least able to report in
> within 20-30 minutes or so, as compared to hours.
>
> We'll probably continue to tweak the system a bit, but it's at least up
> and running now for HEAD, REL_10 and REL9_6 (older branches don't work
> easily with VS2015, as discussed elsewhere).
>
> If anyone has any specific questions about it or suggestions, please
> feel free to reach out.
>


Good. I notice that it doesn't seem to be running the plpython tests
even though it's configured for python. Looks like we need to adjust
vcregress.pl slightly.


cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

On 2018-04-20 19:55:26 -0400, Stephen Frost wrote:
> Greetings,
> 
> * Andres Freund (andres@anarazel.de) wrote:
> > It's common that half the buildfarm has reported back before a single
> > windows buildfarm animal reports. And if they report a failure one often
> > has to wait for hours for the next run.
> 
> Yes, that's been rather annoying.
> 
> > It'd be awesome if somebody could set up a windows animal that runs
> > frequently (i.e. checks for build needed every minute or five) and is
> > fast enough to not take ages to finish a build.
> 
> Done.
> 
> 'dory' was approved today which checks for new commits every 5 minutes
> and, as an added bonus, builds with a somewhat more recent version of
> Visual Studio (2015) and a recent Windows Server version (2016) as
> compared to the other Windows systems.  While it's still not quite as
> fast as our faster buildfarm animals, it's at least able to report in
> within 20-30 minutes or so, as compared to hours.
> 
> We'll probably continue to tweak the system a bit, but it's at least up
> and running now for HEAD, REL_10 and REL9_6 (older branches don't work
> easily with VS2015, as discussed elsewhere).
> 
> If anyone has any specific questions about it or suggestions, please
> feel free to reach out.

Thanks!

Greetings,

Andres Freund