Re: [Pgbuildfarm-members] A few PG buildfarm members need to be restarted(?)

The following buildfarm members haven't reported on HEAD in more than a
week:

tick
leech
markhor
stilt
protosciurus
castoroides

Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
because of the plpython bug Peter E. introduced awhile back. That is
believed to be fixed now, but you'll probably have to manually kill the
current run to get it unstuck.

regards, tom lane

Casteroides and protosciurus appear to be stuck as the most recent
update to the BF code now seems to want the LWP perl module, which
wasn't installed. I've added that - will see if they recover.

On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The following buildfarm members haven't reported on HEAD in more than a
> week:
>
> tick
> leech
> markhor
> stilt
> protosciurus
> castoroides
>
> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
> because of the plpython bug Peter E. introduced awhile back. That is
> believed to be fixed now, but you'll probably have to manually kill the
> current run to get it unstuck.
>
> regards, tom lane
> _______________________________________________
> Pgbuildfarm-members mailing list
> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

That's very odd.

LWP has been a requirement from Day 1 of the buildfarm. It's what's used
to load the results to the server. There have been special
considerations for older Msys systems, so that you run the main script
with Msys perl, which used not to have LWP, and the web script with
ActivePerl, which does, but that shouldn't apply on Solaris.

cheers

andrew

On 05/18/2015 04:57 AM, Dave Page wrote:
> Casteroides and protosciurus appear to be stuck as the most recent
> update to the BF code now seems to want the LWP perl module, which
> wasn't installed. I've added that - will see if they recover.
>
> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The following buildfarm members haven't reported on HEAD in more than a
>> week:
>>
>> tick
>> leech
>> markhor
>> stilt
>> protosciurus
>> castoroides
>>
>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
>> because of the plpython bug Peter E. introduced awhile back. That is
>> believed to be fixed now, but you'll probably have to manually kill the
>> current run to get it unstuck.
>>
>> regards, tom lane
>> _______________________________________________
>> Pgbuildfarm-members mailing list
>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>
>

Hmm, well apparently installing LWP using cpan as root didn't help
anyway - I'm still getting:

On Mon, May 18, 2015 at 11:33 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> That's very odd.
>
> LWP has been a requirement from Day 1 of the buildfarm. It's what's used to
> load the results to the server. There have been special considerations for
> older Msys systems, so that you run the main script with Msys perl, which
> used not to have LWP, and the web script with ActivePerl, which does, but
> that shouldn't apply on Solaris.
>
> cheers
>
> andrew
>
>
>
> On 05/18/2015 04:57 AM, Dave Page wrote:
>>
>> Casteroides and protosciurus appear to be stuck as the most recent
>> update to the BF code now seems to want the LWP perl module, which
>> wasn't installed. I've added that - will see if they recover.
>>
>> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>
>>> The following buildfarm members haven't reported on HEAD in more than a
>>> week:
>>>
>>> tick
>>> leech
>>> markhor
>>> stilt
>>> protosciurus
>>> castoroides
>>>
>>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
>>> because of the plpython bug Peter E. introduced awhile back. That is
>>> believed to be fixed now, but you'll probably have to manually kill the
>>> current run to get it unstuck.
>>>
>>> regards, tom lane
>>> _______________________________________________
>>> Pgbuildfarm-members mailing list
>>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>
>>
>>
>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Argh - sent too soon...

I'm still getting:

Can't locate LWP.pm in @INC (@INC contains:
/usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib
/usr/perl5/site_perl/5.8.4/sun4-solaris-64int
/usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl
/usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int
/usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl .) at
PGBuild/WebTxn.pm line 29.
BEGIN failed--compilation aborted at PGBuild/WebTxn.pm line 35.
Compilation failed in require at ./run_build.pl line 77.
BEGIN failed--compilation aborted at ./run_build.pl line 77.

Upon looking further, it seems that my previous versions of
run_web_txn.pl all start with:

#!/opt/csw/bin/perl

Which makes sense, as that seems to be the default Perl on here.
Clearly I must have changed that script years ago to ensure this
worked (that Perl installation does have LWP installed).

Anyway, I've updated the script again - firing off a build now.

On Mon, May 18, 2015 at 11:40 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hmm, well apparently installing LWP using cpan as root didn't help
> anyway - I'm still getting:
>
>
> On Mon, May 18, 2015 at 11:33 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>
>> That's very odd.
>>
>> LWP has been a requirement from Day 1 of the buildfarm. It's what's used to
>> load the results to the server. There have been special considerations for
>> older Msys systems, so that you run the main script with Msys perl, which
>> used not to have LWP, and the web script with ActivePerl, which does, but
>> that shouldn't apply on Solaris.
>>
>> cheers
>>
>> andrew
>>
>>
>>
>> On 05/18/2015 04:57 AM, Dave Page wrote:
>>>
>>> Casteroides and protosciurus appear to be stuck as the most recent
>>> update to the BF code now seems to want the LWP perl module, which
>>> wasn't installed. I've added that - will see if they recover.
>>>
>>> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>>
>>>> The following buildfarm members haven't reported on HEAD in more than a
>>>> week:
>>>>
>>>> tick
>>>> leech
>>>> markhor
>>>> stilt
>>>> protosciurus
>>>> castoroides
>>>>
>>>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
>>>> because of the plpython bug Peter E. introduced awhile back. That is
>>>> believed to be fixed now, but you'll probably have to manually kill the
>>>> current run to get it unstuck.
>>>>
>>>> regards, tom lane
>>>> _______________________________________________
>>>> Pgbuildfarm-members mailing list
>>>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>>>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>>
>>>
>>>
>>
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

<sigh>. So now apparently the version of git on this box is too old,
as it doesn't support --porcelain. Attempting to build a new one.

On Mon, May 18, 2015 at 11:54 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Argh - sent too soon...
>
> I'm still getting:
>
> Can't locate LWP.pm in @INC (@INC contains:
> /usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib
> /usr/perl5/site_perl/5.8.4/sun4-solaris-64int
> /usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl
> /usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int
> /usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl .) at
> PGBuild/WebTxn.pm line 29.
> BEGIN failed--compilation aborted at PGBuild/WebTxn.pm line 35.
> Compilation failed in require at ./run_build.pl line 77.
> BEGIN failed--compilation aborted at ./run_build.pl line 77.
>
> Upon looking further, it seems that my previous versions of
> run_web_txn.pl all start with:
>
> #!/opt/csw/bin/perl
>
> Which makes sense, as that seems to be the default Perl on here.
> Clearly I must have changed that script years ago to ensure this
> worked (that Perl installation does have LWP installed).
>
> Anyway, I've updated the script again - firing off a build now.
>
> On Mon, May 18, 2015 at 11:40 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> Hmm, well apparently installing LWP using cpan as root didn't help
>> anyway - I'm still getting:
>>
>>
>> On Mon, May 18, 2015 at 11:33 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>>
>>> That's very odd.
>>>
>>> LWP has been a requirement from Day 1 of the buildfarm. It's what's used to
>>> load the results to the server. There have been special considerations for
>>> older Msys systems, so that you run the main script with Msys perl, which
>>> used not to have LWP, and the web script with ActivePerl, which does, but
>>> that shouldn't apply on Solaris.
>>>
>>> cheers
>>>
>>> andrew
>>>
>>>
>>>
>>> On 05/18/2015 04:57 AM, Dave Page wrote:
>>>>
>>>> Casteroides and protosciurus appear to be stuck as the most recent
>>>> update to the BF code now seems to want the LWP perl module, which
>>>> wasn't installed. I've added that - will see if they recover.
>>>>
>>>> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>>>
>>>>> The following buildfarm members haven't reported on HEAD in more than a
>>>>> week:
>>>>>
>>>>> tick
>>>>> leech
>>>>> markhor
>>>>> stilt
>>>>> protosciurus
>>>>> castoroides
>>>>>
>>>>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
>>>>> because of the plpython bug Peter E. introduced awhile back. That is
>>>>> believed to be fixed now, but you'll probably have to manually kill the
>>>>> current run to get it unstuck.
>>>>>
>>>>> regards, tom lane
>>>>> _______________________________________________
>>>>> Pgbuildfarm-members mailing list
>>>>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>>>>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

That must be a very old git, dating from before Sept 2009
(<http://osdir.com/ml/git/2009-09/msg00290.html>), which is before
Postgres even started using git.

I switched to porcelain format precisely because it is guaranteed not to
change, and I got sick of constant breakage when they changed status
messages every release.

cheers

andrew

On 05/18/2015 07:28 AM, Dave Page wrote:
> <sigh>. So now apparently the version of git on this box is too old,
> as it doesn't support --porcelain. Attempting to build a new one.
>
> On Mon, May 18, 2015 at 11:54 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> Argh - sent too soon...
>>
>> I'm still getting:
>>
>> Can't locate LWP.pm in @INC (@INC contains:
>> /usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib
>> /usr/perl5/site_perl/5.8.4/sun4-solaris-64int
>> /usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl
>> /usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int
>> /usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl .) at
>> PGBuild/WebTxn.pm line 29.
>> BEGIN failed--compilation aborted at PGBuild/WebTxn.pm line 35.
>> Compilation failed in require at ./run_build.pl line 77.
>> BEGIN failed--compilation aborted at ./run_build.pl line 77.
>>
>> Upon looking further, it seems that my previous versions of
>> run_web_txn.pl all start with:
>>
>> #!/opt/csw/bin/perl
>>
>> Which makes sense, as that seems to be the default Perl on here.
>> Clearly I must have changed that script years ago to ensure this
>> worked (that Perl installation does have LWP installed).
>>
>> Anyway, I've updated the script again - firing off a build now.
>>
>> On Mon, May 18, 2015 at 11:40 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>> Hmm, well apparently installing LWP using cpan as root didn't help
>>> anyway - I'm still getting:
>>>
>>>
>>> On Mon, May 18, 2015 at 11:33 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>>> That's very odd.
>>>>
>>>> LWP has been a requirement from Day 1 of the buildfarm. It's what's used to
>>>> load the results to the server. There have been special considerations for
>>>> older Msys systems, so that you run the main script with Msys perl, which
>>>> used not to have LWP, and the web script with ActivePerl, which does, but
>>>> that shouldn't apply on Solaris.
>>>>
>>>> cheers
>>>>
>>>> andrew
>>>>
>>>>
>>>>
>>>> On 05/18/2015 04:57 AM, Dave Page wrote:
>>>>> Casteroides and protosciurus appear to be stuck as the most recent
>>>>> update to the BF code now seems to want the LWP perl module, which
>>>>> wasn't installed. I've added that - will see if they recover.
>>>>>
>>>>> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>>>> The following buildfarm members haven't reported on HEAD in more than a
>>>>>> week:
>>>>>>
>>>>>> tick
>>>>>> leech
>>>>>> markhor
>>>>>> stilt
>>>>>> protosciurus
>>>>>> castoroides
>>>>>>
>>>>>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably stuck
>>>>>> because of the plpython bug Peter E. introduced awhile back. That is
>>>>>> believed to be fixed now, but you'll probably have to manually kill the
>>>>>> current run to get it unstuck.
>>>>>>
>>>>>> regards, tom lane
>>>>>> _______________________________________________
>>>>>> Pgbuildfarm-members mailing list
>>>>>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>>>>>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>>>>
>>>>>
>>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>
>>
>> --
>> Dave Page
>> Blog: http://pgsnake.blogspot.com
>> Twitter: @pgsnake
>>
>> EnterpriseDB UK: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>
>

Yeah, 1.6.3. This is an old box don't forget - I'm kinda surprised
that git is there at all. I've built the latest version anyway, and am
re-running....

On Mon, May 18, 2015 at 12:51 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> That must be a very old git, dating from before Sept 2009
> (<http://osdir.com/ml/git/2009-09/msg00290.html>), which is before Postgres
> even started using git.
>
> I switched to porcelain format precisely because it is guaranteed not to
> change, and I got sick of constant breakage when they changed status
> messages every release.
>
> cheers
>
> andrew
>
>
>
> On 05/18/2015 07:28 AM, Dave Page wrote:
>>
>> <sigh>. So now apparently the version of git on this box is too old,
>> as it doesn't support --porcelain. Attempting to build a new one.
>>
>> On Mon, May 18, 2015 at 11:54 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>
>>> Argh - sent too soon...
>>>
>>> I'm still getting:
>>>
>>> Can't locate LWP.pm in @INC (@INC contains:
>>> /usr/perl5/5.8.4/lib/sun4-solaris-64int /usr/perl5/5.8.4/lib
>>> /usr/perl5/site_perl/5.8.4/sun4-solaris-64int
>>> /usr/perl5/site_perl/5.8.4 /usr/perl5/site_perl
>>> /usr/perl5/vendor_perl/5.8.4/sun4-solaris-64int
>>> /usr/perl5/vendor_perl/5.8.4 /usr/perl5/vendor_perl .) at
>>> PGBuild/WebTxn.pm line 29.
>>> BEGIN failed--compilation aborted at PGBuild/WebTxn.pm line 35.
>>> Compilation failed in require at ./run_build.pl line 77.
>>> BEGIN failed--compilation aborted at ./run_build.pl line 77.
>>>
>>> Upon looking further, it seems that my previous versions of
>>> run_web_txn.pl all start with:
>>>
>>> #!/opt/csw/bin/perl
>>>
>>> Which makes sense, as that seems to be the default Perl on here.
>>> Clearly I must have changed that script years ago to ensure this
>>> worked (that Perl installation does have LWP installed).
>>>
>>> Anyway, I've updated the script again - firing off a build now.
>>>
>>> On Mon, May 18, 2015 at 11:40 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>>
>>>> Hmm, well apparently installing LWP using cpan as root didn't help
>>>> anyway - I'm still getting:
>>>>
>>>>
>>>> On Mon, May 18, 2015 at 11:33 AM, Andrew Dunstan <andrew(at)dunslane(dot)net>
>>>> wrote:
>>>>>
>>>>> That's very odd.
>>>>>
>>>>> LWP has been a requirement from Day 1 of the buildfarm. It's what's
>>>>> used to
>>>>> load the results to the server. There have been special considerations
>>>>> for
>>>>> older Msys systems, so that you run the main script with Msys perl,
>>>>> which
>>>>> used not to have LWP, and the web script with ActivePerl, which does,
>>>>> but
>>>>> that shouldn't apply on Solaris.
>>>>>
>>>>> cheers
>>>>>
>>>>> andrew
>>>>>
>>>>>
>>>>>
>>>>> On 05/18/2015 04:57 AM, Dave Page wrote:
>>>>>>
>>>>>> Casteroides and protosciurus appear to be stuck as the most recent
>>>>>> update to the BF code now seems to want the LWP perl module, which
>>>>>> wasn't installed. I've added that - will see if they recover.
>>>>>>
>>>>>> On Sat, May 16, 2015 at 1:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>>>>>
>>>>>>> The following buildfarm members haven't reported on HEAD in more than
>>>>>>> a
>>>>>>> week:
>>>>>>>
>>>>>>> tick
>>>>>>> leech
>>>>>>> markhor
>>>>>>> stilt
>>>>>>> protosciurus
>>>>>>> castoroides
>>>>>>>
>>>>>>> Several of these are using CLOBBER_CACHE_ALWAYS, and are probably
>>>>>>> stuck
>>>>>>> because of the plpython bug Peter E. introduced awhile back. That is
>>>>>>> believed to be fixed now, but you'll probably have to manually kill
>>>>>>> the
>>>>>>> current run to get it unstuck.
>>>>>>>
>>>>>>> regards, tom lane
>>>>>>> _______________________________________________
>>>>>>> Pgbuildfarm-members mailing list
>>>>>>> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
>>>>>>> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> --
>>>> Dave Page
>>>> Blog: http://pgsnake.blogspot.com
>>>> Twitter: @pgsnake
>>>>
>>>> EnterpriseDB UK: http://www.enterprisedb.com
>>>> The Enterprise PostgreSQL Company
>>>
>>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>
>>
>>
>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company