Re: frequent buildd issues with postgis
Dejan, On 10/20/2014 01:21 PM, Dejan Latinovic wrote: Is seems that build fail on Broadcom boards, and pass on cavium and loongson. I will run build locally to confirm this theory. Any results from that exercise? Regards Markus Wanner signature.asc Description: OpenPGP digital signature ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
RE: frequent buildd issues with postgis
Hello Markus, As I suspected, build filed on Broadcom and pass on Cavium board. But I did not figure it out yet what is the reason of this behavior. I am getting the same output like this one: https://buildd.debian.org/status/fetch.php?pkg=postgisarch=mipselver=2.1.4%2Bdfsg-2stamp=1413547028 Regards Dejan From: Markus Wanner [mar...@bluegap.ch] Sent: Thursday, October 23, 2014 11:25 AM To: Dejan Latinovic; debian-m...@lists.debian.org Cc: Debian GIS Project; Christoph Berg Subject: Re: frequent buildd issues with postgis Dejan, On 10/20/2014 01:21 PM, Dejan Latinovic wrote: Is seems that build fail on Broadcom boards, and pass on cavium and loongson. I will run build locally to confirm this theory. Any results from that exercise? Regards Markus Wanner ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Re: frequent buildd issues with postgis
On 10/23/2014 01:35 PM, Dejan Latinovic wrote: As I suspected, build filed on Broadcom and pass on Cavium board. Okay, thanks for your tests and confirmation. But I did not figure it out yet what is the reason of this behavior. I am getting the same output like this one: https://buildd.debian.org/status/fetch.php?pkg=postgisarch=mipselver=2.1.4%2Bdfsg-2stamp=1413547028 These indicate that Postgres restarted for some reason. Leading to connection failures, first. Then, during the restart, the is in recovery mode errors. The Postgres log should have some indication of why it restarted in the first place. Regards Markus ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
frequent buildd issues with postgis
Hi, the postgis package quite frequently fails to build on mips and/or mipsel buildd boxes. That was the case for the last two uploads, both blocking migration to testing. The issue clearly is intermittent and I suspect it's memory related. However, fact is that there's a clear pattern of which buildd boxes could and which couldn't build the package is the past. Since 2.1.1-4 [0], the following boxes have constantly built postgis successfully: eberlin (mipsel, 7x) corelli (mips, 6x) lucatelli (mips, 4x) eysler (mipsel, 2x) These constantly failed: rem (mipsel, 4x) mayer (mipsel, 2x) ball (mips, 2x) swarm (mips, 1x) I didn't find a single machine that switched between successes and failures, since that point in time. I'm currently unable to find any information about these machines; like how much memory each has (db.debian.org seems down). However, maybe you can see a pattern right away? If so, can you establish some kind of rule to make wanna-build chose known-good buildd machines? So that builds are more likely to succeed in the future? And for now: Can you please trigger a rebuild of the latest postgis revision on mipsel, so 2.1.4 can migrate to testing (before the freeze)? Thanks in advance. Regards Markus Wanner [0]: We had portability issues in the past. Judging from other architecture's successes or failures, postgis-2.1.1-4 seems to be the first reasonably portable variant, where I suspect most failures to be intermittent. signature.asc Description: OpenPGP digital signature ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
RE: frequent buildd issues with postgis
Hi, Is seems that build fail on Broadcom boards, and pass on cavium and loongson. I will run build locally to confirm this theory. Regards, Dejan From: Markus Wanner [mar...@bluegap.ch] Sent: Monday, October 20, 2014 8:38 AM To: debian-m...@lists.debian.org Cc: Debian GIS Project Subject: frequent buildd issues with postgis Hi, the postgis package quite frequently fails to build on mips and/or mipsel buildd boxes. That was the case for the last two uploads, both blocking migration to testing. The issue clearly is intermittent and I suspect it's memory related. However, fact is that there's a clear pattern of which buildd boxes could and which couldn't build the package is the past. Since 2.1.1-4 [0], the following boxes have constantly built postgis successfully: eberlin (mipsel, 7x) corelli (mips, 6x) lucatelli (mips, 4x) eysler (mipsel, 2x) These constantly failed: rem (mipsel, 4x) mayer (mipsel, 2x) ball (mips, 2x) swarm (mips, 1x) I didn't find a single machine that switched between successes and failures, since that point in time. I'm currently unable to find any information about these machines; like how much memory each has (db.debian.org seems down). However, maybe you can see a pattern right away? If so, can you establish some kind of rule to make wanna-build chose known-good buildd machines? So that builds are more likely to succeed in the future? And for now: Can you please trigger a rebuild of the latest postgis revision on mipsel, so 2.1.4 can migrate to testing (before the freeze)? Thanks in advance. Regards Markus Wanner [0]: We had portability issues in the past. Judging from other architecture's successes or failures, postgis-2.1.1-4 seems to be the first reasonably portable variant, where I suspect most failures to be intermittent. ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
