Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-05-01 21:19, Mikael Kjellström wrote: Thanks. Will try it out. Just wanted to report that I've tried it and it works as expected. Thanks for the really fast fixes. /Mikael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-05-01 21:10, Andrew Dunstan wrote: Not sure I understand what "rerun a branch" from scratch means. If you zap the branch directory you lose all its state. That's generally a bad thing. I mean like the first time when you set up the buildfarm client / branch. And it's not something I

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 05/01/2017 03:00 PM, Mikael Kjellström wrote: > > On 2017-05-01 20:56, Andrew Dunstan wrote: >> OK, coming up with a more comprehensive fix. > > Ok. > >> The obvious workaround for now is to create the directory and dont zap >> it or its parents. You should only have to do it once (per

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-05-01 20:56, Andrew Dunstan wrote: OK, coming up with a more comprehensive fix. Ok. The obvious workaround for now is to create the directory and dont zap it or its parents. You should only have to do it once (per branch) Yes, I know. That is what I have been doing so far. But

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 05/01/2017 02:46 PM, Mikael Kjellström wrote: > > > On 2017-05-01 20:44, Mikael Kjellström wrote: >> Nope, that didn't do it. > > Or well. It fixed the check_make bug but not the other bug with that > the loach.lastrun-logs-directory isn't created before trying to write > to it. > OK,

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-05-01 20:44, Mikael Kjellström wrote: Nope, that didn't do it. Or well. It fixed the check_make bug but not the other bug with that the loach.lastrun-logs-directory isn't created before trying to write to it. /Mikael -- Sent via pgsql-hackers mailing list

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-05-01 20:25, Andrew Dunstan wrote: OK, that's a bug. Mea culpa. the quick fix is this patch: diff --git a/run_build.pl b/run_build.pl index aeb8966..822b4de 100755 --- a/run_build.pl +++ b/run_build.pl @@ -1008,7 +1008,8 @@ sub writelog sub check_make

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 05/01/2017 02:13 PM, Mikael Kjellström wrote: > On 2017-04-19 15:59, Andrew Dunstan wrote: > > >> I have released version 4.19 of the PostgreSQL Buildfarm client. It can >> be downloaded from >> >> > > I don't know if

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 05/01/2017 02:13 PM, Mikael Kjellström wrote: > On 2017-04-19 15:59, Andrew Dunstan wrote: > > >> I have released version 4.19 of the PostgreSQL Buildfarm client. It can >> be downloaded from >> >> > > I don't know if

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 2017-04-19 15:59, Andrew Dunstan wrote: I have released version 4.19 of the PostgreSQL Buildfarm client. It can be downloaded from I don't know if it's only me or if others have noticed this also but I have the

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

On 04/19/2017 01:38 PM, Tom Lane wrote: > Andrew Dunstan writes: >> I have released version 4.19 of the PostgreSQL Buildfarm client. It can >> be downloaded from >> > Nice work! > Thank

Re: [HACKERS] [buildfarm-members] BuildFarm client release 4.19

Andrew Dunstan writes: > I have released version 4.19 of the PostgreSQL Buildfarm client. It can > be downloaded from > Nice work! > * Improvements to TAP tests logging and coverage. Each