Bug 399601 – [Future EAPI] pkg_notest function which displays reasons for restricting tests in a package

• Product: Portage Development
• Status: RESOLVED WONTFIX

[Description Pacho Ramos 2012-01-21 11:58:43 UTC]

Sometimes we need to skip tests because they are interactive, they are broken... usually we show that reasons in a comment just above "RESTRICT=test". Would be possible to make portage show that commented message when available instead of always show the canonical message of tests being skipped due ebuild restriction? That way we could inform users a bit better about real reasons to skip the test and, how knows... maybe some reader could help on "unbreaking" that tests ;)

Thanks

Reproducible: Always

[Comment 1 Zac Medico 2012-01-21 12:02:59 UTC]

Why not just define the src_test function to display your message? I think it would work well, possibly even better since you'll have the expressive power of bash to do conditional messages if you want.

[Comment 2 Pacho Ramos 2012-01-21 12:09:34 UTC]

But it would be like duplicating the ways of restricting tests, instead of simply using "RESTRICT=test" and a comment above it, we would let tests go for skipping them later :/

[Comment 3 Zac Medico 2012-01-21 12:15:21 UTC]

Hmm, maybe a pkg_notest phase would be a good compromise.

[Comment 4 Zac Medico 2012-01-21 20:43:41 UTC]

Adding pms-bugs to CC, since a pkg_notest extension should be documented there. I imagine it would not be much different from pkg_nofetch. The only difference is that it's called when src_test is skipped due to RESTRICT=test being set.

[Comment 5 Michał Górny 2014-09-06 21:58:29 UTC]

Can be solved using src_test(). Seen no reply in 2.5yr, so assuming interest was lost. WONTFIX.