https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-crypt/hashcat-6.0.0-r1 fails tests. Discovered on: amd64 (internal ref: tinderbox) NOTE: This machine uses a clang/LLVM toolchain. If you think that this issue is strictly related to clang/LLVM please block bug 408963. If you think that this issue is strictly related to the LLD linker, please block bug 731004. This machine uses also GLIBC-2.32. If you think that this issue is strictly related to GLIBC please block bug 736174.
Created attachment 662230 [details] build.log build log and emerge --info
tinderbox_musl has reproduced this issue with version 6.2.5 - Updating summary.
what's the right solution here? Gentoo intentionally doesn't install opencl providers with virtual/opencl, instead, leaving it to the users. This means I can't rely on things to be installed when tests are run. The tests work, but you need to have the right opencl provider for your opencl hardware. I really don't want to disable tests, because I rely on them to check if it work. Is there a way to mark the ebuild so the tinderbox runs don't keep doing this?
Thanks to ionen for teaching me about ALLOW_TEST=all
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1eab86228911911ec6c4efdd2f79adfb3f24090f commit 1eab86228911911ec6c4efdd2f79adfb3f24090f Author: Rick Farina <zerochaos@gentoo.org> AuthorDate: 2023-08-24 02:12:12 +0000 Commit: Rick Farina <zerochaos@gentoo.org> CommitDate: 2023-08-24 02:12:12 +0000 app-crypt/hashcat: restrict test Closes: https://bugs.gentoo.org/744463 Signed-off-by: Rick Farina <zerochaos@gentoo.org> app-crypt/hashcat/hashcat-6.2.6.ebuild | 3 ++- app-crypt/hashcat/hashcat-9999.ebuild | 1 + 2 files changed, 3 insertions(+), 1 deletion(-)
Please add a comment in the ebuild wrt RESTRICT.
