[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#758160: marked as done (gcc-4.9: Please don't run testsuite on sh4)

Your message dated Tue, 26 May 2015 10:21:54 +0200
with message-id <55642D22.5030005@physik.fu-berlin.de>
and subject line Tests can be disabled on the buildds DEB_BUILD_OPTIONS
has caused the Debian Bug report #758160,
regarding gcc-4.9: Please don't run testsuite on sh4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
758160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758160
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:gcc-4.9
Version: 4.9.1-5
Severity: normal

Hello!

Like m68k, our buildds for the sh4 architecture are rather underpowered
and complex source packages may take very long to build.

I am currently building gcc-4.9 manually on one of the sh4 builds which
has been going on for more than a week now, mainly due the testsuite
runs taking very long to finish. Coincidentally I saw gcc-4.9 building
on one of the m68k buildds I am hosting and noticed that the testsuite
isn't run on m68k at all, dramatically reducing the build time.

Thus, I would like to ask to have the testsuite disabled on sh4 as
well in order to avoid build delays for gcc packages on this architecture
in the future.

According to Thorsten Glaser, the necessary changes involve setting the
Build-Dependency dejagnu to [!sh4] in debian/control and adding
check_no_cpus := sh4 to debian/rules.defs, but I assume you know much
better.

I would be great to have this changed soon!

Thanks,
Adrian

--- End Message ---
--- Begin Message --- 
Hi Matthias!

While updating the sbuild configuration on the buildds that I am
maintaining, I actually realized I can just set "nocheck nobench"
in the DEB_BUILD_OPTIONS to disable tests globally for a certain
buildd.

Thus, there is no need to modify the gcc packages for that and we
can close both bug reports.

Cheers,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

--- End Message ---
Reply to: