Re: [Pgbuildfarm-members] Missing Git commit ID in woodlouse status

Hello,

my new animal, woodlouse, shows up on the buildfarm status page with no Git commit ID. The per-run config page shows the normal list of "commits since last run".

What's wrong, and how do I fix it? Git on the machine is 2.7.2 from https://git-for-windows.github.io/.

Thanks,

--
Christian

I will look into it.

chers

andrew

On 03/10/2016 03:44 PM, Christian Ullrich wrote:
> Hello,
>
> my new animal, woodlouse, shows up on the buildfarm status page with no Git commit ID. The per-run config page shows the normal list of "commits since last run".
>
> What's wrong, and how do I fix it? Git on the machine is 2.7.2 from https://git-for-windows.github.io/.
>
> Thanks,
>

It looks like your machine has no log files uploaded at all, which is a
far more serious problem.

What is in C:\buildfarm\buildenv\woodlouse.lastrun-logs ?

cheers

andrew

On 03/10/2016 05:33 PM, Andrew Dunstan wrote:
>
> I will look into it.
>
> chers
>
> andrew
>
>
> On 03/10/2016 03:44 PM, Christian Ullrich wrote:
>> Hello,
>>
>> my new animal, woodlouse, shows up on the buildfarm status page with
>> no Git commit ID. The per-run config page shows the normal list of
>> "commits since last run".
>>
>> What's wrong, and how do I fix it? Git on the machine is 2.7.2 from
>> https://git-for-windows.github.io/.
>>
>> Thanks,
>>
>
> _______________________________________________
> Pgbuildfarm-members mailing list
> Pgbuildfarm-members(at)lists(dot)pgfoundry(dot)org
> http://lists.pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>

* From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]

> It looks like your machine has no log files uploaded at all, which is a
> far more serious problem.
>
> What is in C:\buildfarm\buildenv\woodlouse.lastrun-logs ?

That directory does not exist. I have one in each branch, though. Here is the contents of one:

Verzeichnis von C:\buildfarm\buildenv\REL9_5_STABLE\woodlouse.lastrun-logs

10.03.2016 17:55 <DIR> .
10.03.2016 17:55 <DIR> ..
10.03.2016 17:51 675.828 check-pg_upgrade.log
10.03.2016 17:47 4.153.050 check.log
10.03.2016 17:42 679 configure.log
10.03.2016 17:54 1.247.808 contrib-install-check-C.log
10.03.2016 17:42 40 githead.log
10.03.2016 17:51 1.493 initdb-C.log
10.03.2016 17:52 4.145.447 install-check-C.log
10.03.2016 17:53 2.741.270 isolation-check.log
10.03.2016 17:47 1.906 make-install.log
10.03.2016 17:46 13.444.435 make.log
10.03.2016 17:53 1.029 pl-install-check-C.log
10.03.2016 17:42 400 SCM-checkout.log
10.03.2016 17:51 833 startdb-C-1.log
10.03.2016 17:52 833 startdb-C-2.log
10.03.2016 17:53 833 startdb-C-3.log
10.03.2016 17:53 833 startdb-C-4.log
10.03.2016 17:54 833 startdb-C-5.log
10.03.2016 17:52 609 stopdb-C-1.log
10.03.2016 17:53 495 stopdb-C-2.log
10.03.2016 17:53 495 stopdb-C-3.log
10.03.2016 17:54 495 stopdb-C-4.log
10.03.2016 17:54 496 stopdb-C-5.log
10.03.2016 17:54 65.942 testmodules-install-check-C.log
10.03.2016 17:55 13.542 web-txn.data
24 Datei(en), 26.499.624 Bytes

--
Christian

On 03/11/2016 05:06 AM, Christian Ullrich wrote:
> * From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
>
>> It looks like your machine has no log files uploaded at all, which is a
>> far more serious problem.
>>
>> What is in C:\buildfarm\buildenv\woodlouse.lastrun-logs ?
> That directory does not exist. I have one in each branch, though.

Yes, sorry, that's what I meant.

> Here is the contents of one:
>
> Verzeichnis von C:\buildfarm\buildenv\REL9_5_STABLE\woodlouse.lastrun-logs
>
> 10.03.2016 17:55 <DIR> .
> 10.03.2016 17:55 <DIR> ..
> 10.03.2016 17:51 675.828 check-pg_upgrade.log
> 10.03.2016 17:47 4.153.050 check.log
> 10.03.2016 17:42 679 configure.log
> 10.03.2016 17:54 1.247.808 contrib-install-check-C.log
> 10.03.2016 17:42 40 githead.log
> 10.03.2016 17:51 1.493 initdb-C.log
> 10.03.2016 17:52 4.145.447 install-check-C.log
> 10.03.2016 17:53 2.741.270 isolation-check.log
> 10.03.2016 17:47 1.906 make-install.log
> 10.03.2016 17:46 13.444.435 make.log
> 10.03.2016 17:53 1.029 pl-install-check-C.log
> 10.03.2016 17:42 400 SCM-checkout.log
> 10.03.2016 17:51 833 startdb-C-1.log
> 10.03.2016 17:52 833 startdb-C-2.log
> 10.03.2016 17:53 833 startdb-C-3.log
> 10.03.2016 17:53 833 startdb-C-4.log
> 10.03.2016 17:54 833 startdb-C-5.log
> 10.03.2016 17:52 609 stopdb-C-1.log
> 10.03.2016 17:53 495 stopdb-C-2.log
> 10.03.2016 17:53 495 stopdb-C-3.log
> 10.03.2016 17:54 495 stopdb-C-4.log
> 10.03.2016 17:54 496 stopdb-C-5.log
> 10.03.2016 17:54 65.942 testmodules-install-check-C.log
> 10.03.2016 17:55 13.542 web-txn.data
> 24 Datei(en), 26.499.624 Bytes
>

You don't appear to have a working tar command in the path, since there
is no runlogs.tgz. My MSVC machines get it from msysgit. If your git
installation doesn't include it you might need to install one from
GnuWin32 or some such source.

cheers

andrew

* From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]

> On 03/11/2016 05:06 AM, Christian Ullrich wrote:
> > * From: Andrew Dunstan [mailto:andrew(at)dunslane(dot)net]
> >
> >> It looks like your machine has no log files uploaded at all, which is a
> >> far more serious problem.

> You don't appear to have a working tar command in the path, since there
> is no runlogs.tgz. My MSVC machines get it from msysgit. If your git
> installation doesn't include it you might need to install one from
> GnuWin32 or some such source.

Ah, sorry. I had Git's bin directory in the PATH, but not its usr/bin, where
tar lives.

--
Christian