Gentoo Archives: gentoo-dev

From: Peter Fein <pfein@×××××.com>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] testing during emerge?
Date: Fri, 11 Apr 2003 15:13:07
Message-Id: 20030411101304.383e5fbe.pfein@pobox.com
In Reply to: Re: [gentoo-dev] testing during emerge? by George Shapovalov
1 On Thu, 10 Apr 2003 18:47:56 -0700
2 George Shapovalov <george@g.o> wrote:
3
4 > Well, I guess this can easily be done via another USE flag. I see no reason to
5 > do any changes to portage or anything, just the ebuilds (at least some of
6 > them) should be done to allow optionally run included test suites.
7
8 I was thinking that some portage/ebuild infrastructure might save some code
9 repitition. The problem seems more complicated than doing "make test || die" -
10 especially when you get in to expected failures, etc.. Maybe I'm making this more difficult than it needs to be. ;)
11
12 > And then, I just want to emphasize that this should be optional, as not that
13 > many people will be happy about forced increase in compile time. Thus I think
14 > this is the case where use flag is an ideal approach.
15
16 Choice is good.
17
18 > Then I guess you help can be in the form of submitting diff's against the
19 > ebuilds, where you would like to add optional tests ;). The tests should
20 > apparently be run from within src_compile() (and die on failure).
21
22 I'm willing to take a crack at this, but getting maintainers on board seems useful as it's a natural extension of the configure/build process.
23
24 > Though I somehow feel, that this issue has a potential to grow into a long
25 > discussion thread, what seems to be quite popular lately. So you might want
26 > to hold off for a few days to see how this turns out in the end..
27
28 You don't need to tell me not to work twice. ;)
29
30 --Pete
31
32 > On Thursday 10 April 2003 18:33, Peter Fein wrote:
33 > > Sorry if this has been covered before...
34 > >
35 > > So I recently got hit by the gcc/pentium4 bug, as described here:
36 > > http://forums.gentoo.org/viewtopic.php?t=43373
37 > >
38 > > Why this was particularly annoying is that Python (and lots of other progs)
39 > > include test suites which can catch these sort of things. While this is a
40 > > non-issue for binary distros, being able to run a test suite ("make test"
41 > > or whatever) as part of an emerge would be pretty useful. My ebuild
42 > > experience is somewhat limited (though it doesn't look that hard) though
43 > > I've done a good bit of work in Python. I'd be willing to help out on such
44 > > a project, if there's interest.
45 > >
46 > > --Pete
47 >
48 >
49 > --
50 > gentoo-dev@g.o mailing list
51 >
52 >
53
54
55 --
56 Peter Fein
57 pfein@×××××.com
58 773-575-0694
59
60 --
61 gentoo-dev@g.o mailing list