[opensuse-packaging] berkeleydb -- test phase extremely long
Hello, Please take a look at https://build.opensuse.org/package/live_build_log?arch=ppc&package=berkeleydb&project=openSUSE%3AFactory&repository=standard One can see, that the compilation was ready quickly, but then came a testing phase: 14+ hours!!!! The relevant part of the log: " test-j2ee: BUILD SUCCESSFUL Total time: 891 minutes 17 seconds " Is it really necessary to run such long tests while building a package? This package blocked the compilation for the rest of the packages in Factory PPC for more than half a day. Is there a packaging policy to enable/disable bundled tests? I'll ping package owner (mvyskocil@) if there is no policy against disabling it. Bye, CzP -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, 27 Nov 2009, Peter Czanik wrote:
Hello,
Please take a look at https://build.opensuse.org/package/live_build_log?arch=ppc&package=berkeleydb&project=openSUSE%3AFactory&repository=standard One can see, that the compilation was ready quickly, but then came a testing phase: 14+ hours!!!! The relevant part of the log:
" test-j2ee:
BUILD SUCCESSFUL Total time: 891 minutes 17 seconds "
Is it really necessary to run such long tests while building a package? This package blocked the compilation for the rest of the packages in Factory PPC for more than half a day.
Is there a packaging policy to enable/disable bundled tests? I'll ping package owner (mvyskocil@) if there is no policy against disabling it.
It's good practice to run testsuites when available. If the
testsuites run unreasonably long then either disabling them or
splitting the testsuite run to a separate .spec file is
recommended (see for example gcc which runs the testsuite from
libgcj.spec or ppl which runs the testsuite from ppl-testsuite.spec).
In this particular case I have no idea what the testsuite of
berkeleydb tests - but if it is I/O bound then it's a very
bad idea anyway to run it on the builders.
Richard.
--
Richard Guenther
Am Freitag, 27. November 2009 10:54:45 schrieb Richard Guenther:
On Fri, 27 Nov 2009, Peter Czanik wrote:
Hello,
Please take a look at https://build.opensuse.org/package/live_build_log?arch=ppc&package=berkel eydb&project=openSUSE%3AFactory&repository=standard One can see, that the compilation was ready quickly, but then came a testing phase: 14+ hours!!!! The relevant part of the log:
" test-j2ee:
BUILD SUCCESSFUL Total time: 891 minutes 17 seconds "
Is it really necessary to run such long tests while building a package? This package blocked the compilation for the rest of the packages in Factory PPC for more than half a day.
Is there a packaging policy to enable/disable bundled tests? I'll ping package owner (mvyskocil@) if there is no policy against disabling it.
It's good practice to run testsuites when available. If the testsuites run unreasonably long then either disabling them or splitting the testsuite run to a separate .spec file is recommended (see for example gcc which runs the testsuite from libgcj.spec or ppl which runs the testsuite from ppl-testsuite.spec).
There is a (not enough known) %check section in spec files. When you add it there, we have later the chance to allow enable or disable the run of the testsuites.
In this particular case I have no idea what the testsuite of berkeleydb tests - but if it is I/O bound then it's a very bad idea anyway to run it on the builders.
well, depends. We should be able to configure this in the project later. But it would be good, if we add the tests in the %check in any case. (So far we do not have this switch, should be easy to add, but I would like to think about the general QA framework as hole first). So they are documentated at the defined place. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Friday 27 of November 2009 08:37:51 Peter Czanik wrote:
Hello,
Please take a look at https://build.opensuse.org/package/live_build_log?arch=ppc&package=berkeley db&project=openSUSE%3AFactory&repository=standard One can see, that the compilation was ready quickly, but then came a testing phase: 14+ hours!!!! The relevant part of the log:
I disabled them (25198), but I'd like to have them enabled at least in a devel project. The combination of %bs_project Java:packages in meta prjconf and %if %{!?bs_project:""} == "Java:packages" in spec was not helpful, because bs_project macro has not been expanded in Java:packages. Is there any way how to do it? Regards Michal Vyskocil
participants (4)
-
Adrian Schröter -
Michal Vyskocil -
Peter Czanik -
Richard Guenther