commit:     dd5142fcbd23a45599fef7c2e3bf0190cf6eb7c4
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep  6 15:53:01 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Sep  6 15:54:16 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd5142fc

dev-libs/jerasure: don't skip test failing w/ F_S_=3

encode_decode.sh fails w/ _FORTIFY_SOURCE=3 but the test is new in the
snapshot we're taking (there were no tests before), and upstream development
is over. I originally skipped the test (or, well, XFAIL'd it), but that
doesn't work when the default is stil _F_S=2 and we only default to _F_S=3
on hardened profiles.

So, let's repurpose the bug toralf failed for the XPASS by dropping the
XFAIL and use the bug to track it failing w/ _F_S=3.

Bug: https://bugs.gentoo.org/960946
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/jerasure/jerasure-2.0.0_p20170410.ebuild | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/dev-libs/jerasure/jerasure-2.0.0_p20170410.ebuild 
b/dev-libs/jerasure/jerasure-2.0.0_p20170410.ebuild
index c62b49c6a355..a970513962f4 100644
--- a/dev-libs/jerasure/jerasure-2.0.0_p20170410.ebuild
+++ b/dev-libs/jerasure/jerasure-2.0.0_p20170410.ebuild
@@ -31,12 +31,7 @@ src_prepare() {
 }
 
 src_test() {
-       # encode_decode.sh fails w/ _FORTIFY_SOURCE(=3?) but the test
-       # is new in the snapshot we're taking (there were no tests before),
-       # and upstream development is over, so let's skip the one test unless
-       # someone really wants to investigate it (so we can have unrestricted
-       # tests rather than none running).
-       emake GF_COMPLETE_DIR="${BROOT}"/usr/bin check 
XFAIL_TESTS="encode_decode.sh"
+       emake GF_COMPLETE_DIR="${BROOT}"/usr/bin check
 }
 
 src_install() {

Reply via email to