Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi, On Wed, Sep 09, 2015 at 11:22:10AM +0200, Julien Cristau wrote: > On Wed, Sep 9, 2015 at 09:44:30 +0200, Andreas Tille wrote: > > > Hi mips porters, > > > > could anybody please find a more powerful machine to build the rdepends > > libfreecontact-perl and python-freecontact. > > > No, as

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Wed, Sep 9, 2015 at 3:44 PM, Andreas Tille wrote: > Hi mips porters, > > could anybody please find a more powerful machine to build the rdepends > libfreecontact-perl and python-freecontact. > > Alternatively I would decide to exclude mips architecture for > libfreecontact

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi mips porters, could anybody please find a more powerful machine to build the rdepends libfreecontact-perl and python-freecontact. Alternatively I would decide to exclude mips architecture for libfreecontact and its Perl and Python interfaces since I see no point in delivering a package that

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Wed, Sep 9, 2015 at 09:44:30 +0200, Andreas Tille wrote: > Hi mips porters, > > could anybody please find a more powerful machine to build the rdepends > libfreecontact-perl and python-freecontact. > No, as I already said that is not acceptable. Packages should be built on buildds.

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Control: reopen -1 On Fri, Aug 28, 2015 at 17:42:10 +0200, Andreas Tille wrote: > Hi Julien, > > On Fri, Aug 28, 2015 at 05:20:55PM +0200, Julien Cristau wrote: > > On Wed, Aug 26, 2015 at 17:05:39 +0200, Andreas Tille wrote: > > > > > Any chance to do a manual build on a more powerfull MIPS

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi Julien, On Fri, Aug 28, 2015 at 05:20:55PM +0200, Julien Cristau wrote: On Wed, Aug 26, 2015 at 17:05:39 +0200, Andreas Tille wrote: Any chance to do a manual build on a more powerfull MIPS box which might not run into this problem? NAK. We need packages to build reliably on our

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Fri, Aug 28, 2015 at 17:42:10 +0200, Andreas Tille wrote: Hi Julien, On Fri, Aug 28, 2015 at 05:20:55PM +0200, Julien Cristau wrote: On Wed, Aug 26, 2015 at 17:05:39 +0200, Andreas Tille wrote: Any chance to do a manual build on a more powerfull MIPS box which might not run into

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Wed, Aug 26, 2015 at 17:05:39 +0200, Andreas Tille wrote: Any chance to do a manual build on a more powerfull MIPS box which might not run into this problem? NAK. We need packages to build reliably on our buildds. Cheers, Julien signature.asc Description: Digital signature

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi, this is obviously a consequence of mips buildd's limitations. In past all three successfully builds had happened on ball. I also was able to built freecontact successfully for mips on machine with FPU, localy. On machine without FPU, if icme_timeout is significantly increased tests

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Fri, 2015-08-28 18:08:33 +, Dejan Latinovic wrote: Hi, this is obviously a consequence of mips buildd's limitations. In past all three successfully builds had happened on ball. I also was able to built freecontact successfully for mips on machine with FPU, locally. On machine without

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hello Andreas! On Wed, 26 Aug 2015 17:05:39 +0200 Andreas Tille ti...@debian.org wrote: Any chance to do a manual build on a more powerfull MIPS box which might not run into this problem? I think we should disable the test suite (override_dh_auto_test). What do you think? Best regards,

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Tue, Aug 25, 2015 at 11:09:27PM +0200, Julien Cristau wrote: On Mon, Aug 24, 2015 at 09:32:25 +0200, Andreas Tille wrote: I wonder whether this might be connected to some transition issue. At least I have no idea how to track this down. Its no upstream version and before I did the

Bug#796731: freecontact: FTBFS on mips (test suite failure)

https://dsa.debian.org/doc/schroot On August 26, 2015 1:36:45 PM CEST, Andreas Tille ti...@debian.org wrote: On Tue, Aug 25, 2015 at 11:09:27PM +0200, Julien Cristau wrote: On Mon, Aug 24, 2015 at 09:32:25 +0200, Andreas Tille wrote: I wonder whether this might be connected to some

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi, I had tried to build freecontact locally on two different cavium boards. On both board build failed with TERM signal error on testing. It seems that this is the command that causes TERM signal: /build/freecontact-hkgMtc/freecontact-1.0.21/src/.libs/lt-freecontact --parprof=psicov

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi Dejan, On Wed, Aug 26, 2015 at 02:44:50PM +, Dejan Latinovic wrote: I had tried to build freecontact locally on two different cavium boards. Thanks for this. (I'm running the build on gabrielli currently ... and yes, it takes time). On both board build failed with TERM signal error on

Bug#796731: freecontact: FTBFS on mips (test suite failure)

On Mon, Aug 24, 2015 at 09:32:25 +0200, Andreas Tille wrote: Hi Mips porters, I wonder whether this might be connected to some transition issue. At least I have no idea how to track this down. Its no upstream version and before I did the gcc transition of libfreecontact everything went

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Hi Mips porters, I wonder whether this might be connected to some transition issue. At least I have no idea how to track this down. Its no upstream version and before I did the gcc transition of libfreecontact everything went fine. Any help would be welcome Andreas. On Sun, Aug 23,

Bug#796731: freecontact: FTBFS on mips (test suite failure)

Source: freecontact Version: 1.0.21-4 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package failed to build on the mips buildd, see the log at