| 1 |
Hi, |
| 2 |
|
| 3 |
On Fri, Jun 4, 2010 at 10:41 AM, "Paweł Hajdan, Jr." |
| 4 |
<phajdan.jr@g.o> wrote: |
| 5 |
> What do you think about doing the following change in |
| 6 |
> /usr/portage/profiles/targets/developer/make.defaults: |
| 7 |
> |
| 8 |
> replace "test" with "test-fail-continue" to make it just less |
| 9 |
> frustrating (we still have a lot of test failures) |
| 10 |
|
| 11 |
I've been thinking about this for a while. Some packages have tests |
| 12 |
that are meant only for upstream in certain conditions |
| 13 |
and are not meant to be ran during installing. As we have ARCH teams, |
| 14 |
couldn't we think a way in which TEST teams can |
| 15 |
be created? I mean, a bunch of devs only focused on making tests work |
| 16 |
or just restrict them? |
| 17 |
|
| 18 |
This team (or a Gentoo project) can work hand by hand with other teams |
| 19 |
and ARCH members. |
| 20 |
|
| 21 |
Is it even possible? |
| 22 |
|
| 23 |
> |
| 24 |
> Hopefully that will also make more of us use the developer profile, and |
| 25 |
> detect test failures. |
| 26 |
> |
| 27 |
> What do you think? |
| 28 |
> |
| 29 |
> Paweł |
| 30 |
|
| 31 |
Best regards, |
| 32 |
|
| 33 |
-- |
| 34 |
Jesus Rivero (Neurogeek) |
Archives