On Fri, 2012-04-27 at 15:30 +0200, Thomas Spura wrote:
> On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen wrote:
> > On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote:
> >
> >>
> >> Apart of this, there are test-cases, which can not be/can not be easily
> >> executed inside of a mock-environ
> On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen
> wrote:
> > On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote:
> >
> >>
> >> Apart of this, there are test-cases, which can not be/can not be
> >> easily
> >> executed inside of a mock-environment as part of building.
> >
> > Not to mention
On Fri, Apr 27, 2012 at 3:26 PM, Matthias Clasen wrote:
> On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote:
>
>>
>> Apart of this, there are test-cases, which can not be/can not be easily
>> executed inside of a mock-environment as part of building.
>
> Not to mention that running extensive
On Fri, 2012-04-27 at 14:33 +0200, Ralf Corsepius wrote:
>
> Apart of this, there are test-cases, which can not be/can not be easily
> executed inside of a mock-environment as part of building.
Not to mention that running extensive test suites for every build will
put strain on our build infras
On 04/27/2012 02:11 PM, Matthias Runge wrote:
I wonder how different a run-time test-suite dffers from a test suite to
be executed during build.
There are 2 major differences:
1. The package-to-test itself is not installed to its final destination.
2. A testsuite being run in %check has acce
On 27/04/12 13:57, Michael Schwendt wrote:
> A wrong approach?
>
> Why do you insist on using the %check section for that? It's a build-time
> feature, found only in the spec file and not packaged in the built rpms
> (also due to the test data I've referred to above).
>
I'm asking if the scripts
On Fri, 27 Apr 2012 13:04:56 +0200, MR (Matthias) wrote:
> On 27/04/12 12:37, Michael Schwendt wrote:
>
> > Hardly any %check section uses installed files. Typically, files in the
> > buildroot are used, or files plus test data in the builddir. Test data
> > won't be available.
> >
> We encourag
On 27/04/12 12:37, Michael Schwendt wrote:
> Hardly any %check section uses installed files. Typically, files in the
> buildroot are used, or files plus test data in the builddir. Test data
> won't be available.
>
We encourage our packagers to implement useful check-sections.
To make an example,
On Fri, 27 Apr 2012 12:10:11 +0200, MR (Matthias) wrote:
> Hi,
>
> just a half-baked idea, I'm carrying some time with me around.
>
> Some packages have a check-section being executed during build. Would it
> make sense to execute that test, when required packages of that package
> get updated (
Hi,
just a half-baked idea, I'm carrying some time with me around.
Some packages have a check-section being executed during build. Would it
make sense to execute that test, when required packages of that package
get updated (to see, if the update breaks my package)?
(Or other way around: when su
10 matches
Mail list logo
