Bug 398659 – sys-apps/portage: add a way to kill test phase and skip it

• Status: RESOLVED WONTFIX
• Product: Portage Development

[Description Pacho Ramos 2012-01-12 12:17:36 UTC]

I think I reported this before, but I am unable to find it :S

I get this again as I am now suffering dev-libs/boost tests, I need to get boost finally installed but, for that, I need to manually start killing random test processes to get test phase failing and, then, continue the installation.

Personally, I would add an option to be able to properly kill test phase and continue (depending on we having "test-fail-continue" FEATURE, of course)

Thanks a lot :)

Reproducible: Always

[Comment 1 Zac Medico 2012-01-12 12:39:41 UTC]

I don't think it's really worth adding a way to kill a specific phase. You can just kill the whole thing and the do `FEATURES=-test ebuild foo.ebuild merge` if you don't want to re-compile from the beginning.

Also, you can use /etc/portage/package.env to set FEATURES="${FEATURES} -test" for specific packages in advance.

[Comment 2 Pacho Ramos 2012-01-12 17:56:59 UTC]

(In reply to comment #1)
> I don't think it's really worth adding a way to kill a specific phase. You can
> just kill the whole thing and the do `FEATURES=-test ebuild foo.ebuild merge`
> if you don't want to re-compile from the beginning.
> 
> Also, you can use /etc/portage/package.env to set FEATURES="${FEATURES} -test"
> for specific packages in advance.

The problem is that, usually, I want to always run tests but, from time to time, I need to "go ahead and install it finally without waiting more and more", but killing the whole think and then doing ebuild merge looks interesting :-/, feel free then to do whatever you want with this, and thanks a lot for the tip :) (and sorry for the inconvenience)

[Comment 3 Zac Medico 2012-01-12 18:06:44 UTC]

Ok, no problem.