Bug 524026 – sys-apps/portage-2.2.14_rc1 fails to run src_test() when FEATURES="test"

• Status: RESOLVED INVALID
• Product: Portage Development

[Description Brian Evans (RETIRED) 2014-09-29 13:26:28 UTC]

Created attachment 385738 [details]
build.log (gzipped)

For several versions now, portage has been failing to execute src_test() when it is enabled with FEATURES.

Portage stable (2.2.8) works fine. 2.2.12 fails.

I run `USE='-cluster embedded extraengine perl ssl static-libs community' FEATURES='test userpriv -usersandbox' ebuild /usr/portage/dev-db/mariadb/mariadb-10.0.14.ebuild digest clean package`

The result is attached in build.log and enviornment

[Comment 1 Brian Evans (RETIRED) 2014-09-29 13:27:51 UTC]

Created attachment 385740 [details]
environment file

[Comment 2 Zac Medico 2014-09-29 15:17:26 UTC]

The build log shows that FEATURES=test is disabled:

>>> Test phase [not enabled]: dev-db/mariadb-10.0.14

It should be that have the something disabling FEATURES=test inside /etc/portage/package.env, /etc/portage/env, or /etc/portage/bashrc.

[Comment 3 Brian Evans (RETIRED) 2014-09-29 17:04:44 UTC]

(In reply to Zac Medico from comment #2)
> The build log shows that FEATURES=test is disabled:
> 
> >>> Test phase [not enabled]: dev-db/mariadb-10.0.14
> 
> It should be that have the something disabling FEATURES=test inside
> /etc/portage/package.env, /etc/portage/env, or /etc/portage/bashrc.

I did have a /etc/portage/env/dev-db/mariadb file with other FEATURES enabled.
FEATURES="ccache splitdebug compressdebug"

I expected them to be merged.  The build.log did not indicate the env variables were active though.  So what is really happening?

[Comment 4 Zac Medico 2014-09-29 17:50:37 UTC]

For FEATURES settings, you need to use /etc/portage/package.env instead of /etc/portage/env/${CATEGORY}/${PN}. Refer to `man portage` for details.

[Comment 5 Brian Evans (RETIRED) 2014-10-01 13:24:05 UTC]

Thank you for the explanation, it is working as intended.