1 |
On Tuesday 25 September 2007, Bo Ørsted Andresen wrote: |
2 |
> On Tuesday 25 September 2007 12:47:35 Marijn Schouten (hkBst) wrote: |
3 |
> > > > # "make test" does something weird so default src_test() in |
4 |
> > > > /usr/lib/portage/bin/ebuild.sh fails the following test # elif emake |
5 |
> > > > -j1 test -n &> /dev/null; then |
6 |
> > > > # so copy straight from default src_test() all the stuff which |
7 |
> > > > depends on that test passing src_test() { |
8 |
> > > > vecho ">>> Test phase [test]: ${CATEGORY}/${PF}" |
9 |
> > > > if ! emake -j1 test; then |
10 |
> > > > hasq test $FEATURES && die "Make test failed. See above for |
11 |
> > > > details." hasq test $FEATURES || eerror "Make test failed. See above |
12 |
> > > > for details." fi |
13 |
> > > > } |
14 |
> > > |
15 |
> > > I'm a bit confused about what's going on here. Isn't src_test() only |
16 |
> > > supposed to run when 'test' is in FEATURES? |
17 |
> > |
18 |
> > I'm not sure, but as the comment says, I copied this straight from |
19 |
> > /usr/lib/portage/bin/ebuild.sh and it goes: |
20 |
> |
21 |
> [SNIP] |
22 |
> |
23 |
> Some of that code is unreachable since src_test is never called when test |
24 |
> is not in FEATURES. Also there is some dispute as to whether testing the |
25 |
> FEATURES variable at all is permitted in ebuilds (bug #174335). In either |
26 |
> case it's not needed here. if `emake -j1 test -n` really fails for some |
27 |
> reason even though `emake -j1 test` generally works your src_test should |
28 |
> just be: |
29 |
> |
30 |
> src_test() { |
31 |
> emake -j1 test || die "Make test failed" |
32 |
> } |
33 |
|
34 |
why is src_test() defined at all ... the default src_test will execute `emake |
35 |
check` if possible and then try `emake test` |
36 |
-mike |