[gentoo-dev] FEATURES_maketest_question

[gentoo-dev] FEATURES_maketest_question

[Rumen Yotov]

Hi,
Long story short. For some days used 'maketest' in FEATURES - had some
10% failures, so needed to re-emerge the packages w/o 'maketest'.
As this probably is happening during the 'make check/test' phase (after
compilation - if this true in ALL cases) is it possible to continue
(skip test) with just: ebuild ... install/qmerge to finish the process
or not?
Thanks in advance.
-- 
Rumen Yotov <rumen_yotov@dir.bg>

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Joseph Booker]

On Mon, November 29, 2004 12:44 pm, Rumen Yotov said:
> Hi,
> Long story short. For some days used 'maketest' in FEATURES - had some
> 10% failures, so needed to re-emerge the packages w/o 'maketest'.
> As this probably is happening during the 'make check/test' phase (after
> compilation - if this true in ALL cases) is it possible to continue
> (skip test) with just: ebuild ... install/qmerge to finish the process
> or not?
> Thanks in advance.
> --
> Rumen Yotov <rumen_yotov@dir.bg>

You can use the file at http://dev.gentoo.org/~solar/portage_misc/bashrc
(put it in /etc/portage/bashrc) and use a /etc/portage/package.feature
file to turn off the maketest FEATURES flag, and see if it works

-- 
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Mike Gardiner]

Just curious but,

Why do you, as a user, feel it necessary to use FEATURES="maketest"? I'm
just curious as to what motivates some people to use maketest.

Mike Gardiner
(Obz)



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Rumen Yotov]

On пн, 2004-11-29 at 14:49 -0600, Joseph Booker wrote:
> On Mon, November 29, 2004 12:44 pm, Rumen Yotov said:
> > Hi,
> > Long story short. For some days used 'maketest' in FEATURES - had some
> > 10% failures, so needed to re-emerge the packages w/o 'maketest'.
> > As this probably is happening during the 'make check/test' phase (after
> > compilation - if this true in ALL cases) is it possible to continue
> > (skip test) with just: ebuild ... install/qmerge to finish the process
> > or not?
> > Thanks in advance.
> > --
> > Rumen Yotov <rumen_yotov@dir.bg>
> 
> You can use the file at http://dev.gentoo.org/~solar/portage_misc/bashrc
> (put it in /etc/portage/bashrc) and use a /etc/portage/package.feature
> file to turn off the maketest FEATURES flag, and see if it works
> 
Hi,
Thanks for the answer, as i'm already using this plus some settings
in /etc/make.conf - FEATURES="...maketest..." and while emerging they
get added so things work. May be it would be better to put 'maketest' in
package.feature as it'll be on a per package base (must check) and not
global.
But my main issue here is with the time/resources needed to recompile
the failing (?) package/s. i just want to skip testing phase w/o
recompiling.
Even more this (failing) may be due to some gentoo specific
patches/configs so one way for things to be resolved is upstream but
here gentoo may not be a general case or be needed that some dev
explicitly disables some checks/tests - time/resources needed again.
For example look at a BUG about libtool (i'm getting this too) where
failing 'sh.test' (only 1 of 109) is due to gentoo patch and so can't be
fixed upstream. By memory i've such errors with libtool,cdemu,gnome-vfs
and some 3-4 more.
And as in my experience i have nearly 10% emerge errors due to
'maketest' this becomes an issue.
Consider if i should use 'maketest' at all? i'll if there is a way for
this to be useful w/o too many problems. Also new bugs should emerge.
Now just search for an easier way to use this (skip testing phase) and
don't waste time/resources.
TIA
-- 
Rumen Yotov <rumen_yotov@dir.bg>

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Mike Gardiner]

> Personally, I use it because it gives me extra checks that a package
> is working correctly before I merge into my system and potentially
> break things.  Since I am mostly using non-x86 this becomes more
> likely.

So peace of mind is your motivation?

> Btw, if we (as users) run into a package that fails maketest, is opening
> a bug the right thing to do?

I can't speak for all packages, but for GNOME packages, we'll take
patches you can provide that fix "make test" errors, but we don't have
time to look into fixing the tests ourselves.

Unfortunately, "make test" isn't uniformly adhered to upstream, and in
my experience, the tests that are conducted with it are often outdated,
and/or unmaintained. In these cases, "make test" doesn't provide any
indication of the state of the software - if it's
runnable/testable/linkable/however the tests are conducted.

This said, I'm not aware of (any?) Gentoo policy/stance on this, if
anyone can fill me in on that, please do.

Mike Gardiner
(Obz)




--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Paul de Vrieze]

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

On Tuesday 30 November 2004 05:50, Rumen Yotov wrote:
> Hi,
> Thanks for the answer, as i'm already using this plus some settings
> in /etc/make.conf - FEATURES="...maketest..." and while emerging they
> get added so things work. May be it would be better to put 'maketest'
> in package.feature as it'll be on a per package base (must check) and
> not global.
> But my main issue here is with the time/resources needed to recompile
> the failing (?) package/s. i just want to skip testing phase w/o
> recompiling.

Try to use the ebuild command. 

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] FEATURES_maketest_question

[Chris L. Mason]

On Tue, 30 Nov 2004 06:53:09 +0800, Mike Gardiner <obz@gentoo.org> wrote:
> Just curious but,
> 
> Why do you, as a user, feel it necessary to use FEATURES="maketest"? I'm
> just curious as to what motivates some people to use maketest.
> 

Personally, I use it because it gives me extra checks that a package
is working correctly before I merge into my system and potentially
break things.  Since I am mostly using non-x86 this becomes more
likely.

Btw, if we (as users) run into a package that fails maketest, is opening
a bug the right thing to do?

Thanks,


Chris

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Rumen Yotov]

Hi,
On вт, 2004-11-30 at 15:54 +0800, Mike Gardiner wrote:
> > Personally, I use it because it gives me extra checks that a package
> > is working correctly before I merge into my system and potentially
> > break things.  Since I am mostly using non-x86 this becomes more
> > likely.
> 
> So peace of mind is your motivation?
> 
In my case not just peace of mind but looking for an extra functionality
make test could give, but not extra problems.
> > Btw, if we (as users) run into a package that fails maketest, is opening
> > a bug the right thing to do?
> 
> I can't speak for all packages, but for GNOME packages, we'll take
> patches you can provide that fix "make test" errors, but we don't have
> time to look into fixing the tests ourselves.
> 
> Unfortunately, "make test" isn't uniformly adhered to upstream, and in
> my experience, the tests that are conducted with it are often outdated,
> and/or unmaintained. In these cases, "make test" doesn't provide any
> indication of the state of the software - if it's
> runnable/testable/linkable/however the tests are conducted.
> 
That's what i also suspected.
> This said, I'm not aware of (any?) Gentoo policy/stance on this, if
> anyone can fill me in on that, please do.
> 
> Mike Gardiner
> (Obz)
> 
> 
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
Thanks.
-- 
Rumen Yotov <rumen_yotov@dir.bg>

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Rumen Yotov]

On вт, 2004-11-30 at 13:49 +0100, Paul de Vrieze wrote:
> On Tuesday 30 November 2004 05:50, Rumen Yotov wrote:
> > Hi,
> > Thanks for the answer, as i'm already using this plus some settings
> > in /etc/make.conf - FEATURES="...maketest..." and while emerging they
> > get added so things work. May be it would be better to put 'maketest'
> > in package.feature as it'll be on a per package base (must check) and
> > not global.
> > But my main issue here is with the time/resources needed to recompile
> > the failing (?) package/s. i just want to skip testing phase w/o
> > recompiling.
> 
> Try to use the ebuild command. 
> 
> Paul
> 
Hi,
Will try.
Thanks.
-- 
Rumen Yotov <rumen_yotov@dir.bg>

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] FEATURES_maketest_question

[Joseph Booker]

On Tue, November 30, 2004 12:25 pm, Rumen Yotov said:
> On вт, 2004-11-30 at 13:49 +0100, Paul de Vrieze wrote:
>> On Tuesday 30 November 2004 05:50, Rumen Yotov wrote:
>> > Hi,
>> > Thanks for the answer, as i'm already using this plus some settings
>> > in /etc/make.conf - FEATURES="...maketest..." and while emerging they
>> > get added so things work. May be it would be better to put 'maketest'
>> > in package.feature as it'll be on a per package base (must check) and
>> > not global.
>> > But my main issue here is with the time/resources needed to recompile
>> > the failing (?) package/s. i just want to skip testing phase w/o
>> > recompiling.
>>
>> Try to use the ebuild command.
>>
>> Paul
>>
> Hi,
> Will try.
> Thanks.
> --
> Rumen Yotov <rumen_yotov@dir.bg>
>

Theres also ccache

-- 
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net


--
gentoo-dev@gentoo.org mailing list