Bug#767291: closed by Andreas Tille (Re: Bug#767291: blitz++: FTBFS on mips)
Hi Andreas, On Sun, Nov 02, 2014 at 10:48:10AM +, Debian Bug Tracking System wrote: > since Dejan confirmed that the problem is not in the package itself and > it builds *in principle* on mips I hereby close this bug to ensure that > the migration will not only be blocked because of this bug once the mips > porters took the needed means to build the package successfully. > > Ivo, I hope you agree with this, if not please reopen. I don't mind, but blitz++ still won't migrate to testing like this. For that to happen, the build needs to succeed or the old mips packages need to be removed (including rdeps). This needs to happen before the freeze deadline (Nov 5th). It probably doesn't matter that much, as there is another RC bug preventing the migration anyway (#767564). Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767291: closed by Andreas Tille (Re: Bug#767291: blitz++: FTBFS on mips)
Hi Ivo, On Sun, Nov 02, 2014 at 11:59:41AM +0100, Ivo De Decker wrote: > Hi Andreas, > > On Sun, Nov 02, 2014 at 10:48:10AM +, Debian Bug Tracking System wrote: > > since Dejan confirmed that the problem is not in the package itself and > > it builds *in principle* on mips I hereby close this bug to ensure that > > the migration will not only be blocked because of this bug once the mips > > porters took the needed means to build the package successfully. > > > > Ivo, I hope you agree with this, if not please reopen. > > I don't mind, but blitz++ still won't migrate to testing like this. For that > to happen, the build needs to succeed or the old mips packages need to be > removed (including rdeps). This needs to happen before the freeze deadline > (Nov 5th). Sure. I know this and I just have sent two mails to debian-mips list that I will ask for removal of there will be no progress (even before you sent the bug ;-)). > It probably doesn't matter that much, as there is another RC bug preventing > the migration anyway (#767564). Since I uploaded a fix for the said bug before I closed this one and now also asked for unblock I think it now only depends from debian-mips people how honest they are about their port. I'll ask ftpmaster for removal from mips three days before the migration period ends. Thanks for your attention anyway Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767291: blitz++: FTBFS on mips
Hi Dejan, On Thu, Oct 30, 2014 at 10:49:24AM +, Dejan Latinovic wrote: > Maybe it is possible to blacklist blitz++ on cavium machines, > and try to build it on broadcom board (ball, swarm). Thanks for your test that seems to prove my expectation. Anybody able to to the according blacklisting? Thanks Andreas > I had tested it locally. > On cavium board, > build fail with TERM signal. > If tests are ran manually, all tests pass, > but requires a lot of time. > > Actually, the array test is the one that > causes this failure. > All other tests executes significantly faster. > (1-10 min). > > Duration of array test execution on cavium board is: > 304m40.451s. > > > On broadcom board, > package builds successfully. > Duration of array test execution on broadcom board is: > 12m50.570s. > > > Best Regards, > Dejna > > > > > From: Andreas Tille [andr...@an3as.eu] > Sent: Thursday, October 30, 2014 8:53 AM > To: 767...@bugs.debian.org > Cc: debian-m...@lists.debian.org > Subject: Re: Bug#767291: blitz++: FTBFS on mips > > Hi Ivo, > > thanks for the bug report. > > On Wed, Oct 29, 2014 at 10:14:00PM +0100, Ivo De Decker wrote: > > package: blitz++ > > version: 1:0.10-2 > > severity: serious > > > > It seems the latest upload of blitz++ failed on mips, but it built fine > > before. This prevents migration to testing. > > I'm aware of this fact ind just contacted mips porters[1]. I had the > experience with several other packages that this is due to a not as > powerful enough build machine. The build failure [2] > > ... > Running examples... > E: Caught signal ‘Terminated’: terminating immediately > > could leat to the conclusion that this is the case here as well. As I > explained in my mail to the mips porters[1] my personal solution to deal > with this would be to ask ftpmasters to remove the package for mips > architecture to enable a migration to testing. I will wait until the > end of the weekend for any response to find a better solution before > I'll do this. > > Kind regards > > Andreas. > > > [1] https://lists.debian.org/debian-mips/2014/10/msg00021.html > [2] https://buildd.debian.org/status/package.php?p=blitz%2B%2B&suite=sid > > https://buildd.debian.org/status/fetch.php?pkg=blitz%2B%2B&arch=mips&ver=1%3A0.10-2&stamp=1412974511 > > -- > http://fam-tille.de > > > -- > To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20141030075301.ga17...@an3as.eu -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767291: blitz++: FTBFS on mips
Hello, Maybe it is possible to blacklist blitz++ on cavium machines, and try to build it on broadcom board (ball, swarm). I had tested it locally. On cavium board, build fail with TERM signal. If tests are ran manually, all tests pass, but requires a lot of time. Actually, the array test is the one that causes this failure. All other tests executes significantly faster. (1-10 min). Duration of array test execution on cavium board is: 304m40.451s. On broadcom board, package builds successfully. Duration of array test execution on broadcom board is: 12m50.570s. Best Regards, Dejna From: Andreas Tille [andr...@an3as.eu] Sent: Thursday, October 30, 2014 8:53 AM To: 767...@bugs.debian.org Cc: debian-m...@lists.debian.org Subject: Re: Bug#767291: blitz++: FTBFS on mips Hi Ivo, thanks for the bug report. On Wed, Oct 29, 2014 at 10:14:00PM +0100, Ivo De Decker wrote: > package: blitz++ > version: 1:0.10-2 > severity: serious > > It seems the latest upload of blitz++ failed on mips, but it built fine > before. This prevents migration to testing. I'm aware of this fact ind just contacted mips porters[1]. I had the experience with several other packages that this is due to a not as powerful enough build machine. The build failure [2] ... Running examples... E: Caught signal ‘Terminated’: terminating immediately could leat to the conclusion that this is the case here as well. As I explained in my mail to the mips porters[1] my personal solution to deal with this would be to ask ftpmasters to remove the package for mips architecture to enable a migration to testing. I will wait until the end of the weekend for any response to find a better solution before I'll do this. Kind regards Andreas. [1] https://lists.debian.org/debian-mips/2014/10/msg00021.html [2] https://buildd.debian.org/status/package.php?p=blitz%2B%2B&suite=sid https://buildd.debian.org/status/fetch.php?pkg=blitz%2B%2B&arch=mips&ver=1%3A0.10-2&stamp=1412974511 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141030075301.ga17...@an3as.eu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767291: blitz++: FTBFS on mips
Hi Ivo, thanks for the bug report. On Wed, Oct 29, 2014 at 10:14:00PM +0100, Ivo De Decker wrote: > package: blitz++ > version: 1:0.10-2 > severity: serious > > It seems the latest upload of blitz++ failed on mips, but it built fine > before. This prevents migration to testing. I'm aware of this fact ind just contacted mips porters[1]. I had the experience with several other packages that this is due to a not as powerful enough build machine. The build failure [2] ... Running examples... E: Caught signal ‘Terminated’: terminating immediately could leat to the conclusion that this is the case here as well. As I explained in my mail to the mips porters[1] my personal solution to deal with this would be to ask ftpmasters to remove the package for mips architecture to enable a migration to testing. I will wait until the end of the weekend for any response to find a better solution before I'll do this. Kind regards Andreas. [1] https://lists.debian.org/debian-mips/2014/10/msg00021.html [2] https://buildd.debian.org/status/package.php?p=blitz%2B%2B&suite=sid https://buildd.debian.org/status/fetch.php?pkg=blitz%2B%2B&arch=mips&ver=1%3A0.10-2&stamp=1412974511 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767291: blitz++: FTBFS on mips
package: blitz++ version: 1:0.10-2 severity: serious Hi, It seems the latest upload of blitz++ failed on mips, but it built fine before. This prevents migration to testing. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
