https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-ruby/rake-13.0.6-r1 fails tests (MUSL). Discovered on: amd64 (internal ref: tinderbox_musl) NOTE: This machine uses MUSL libc
Created attachment 802111 [details] build.log build log and emerge --info
I'm now seeing this same test failure (which I've never seen before) in my glibc mostly-stable hardened amd64 box when trying to upgrade rake-13.0.6-r2 from ruby30 to ruby31.
Same for me :/
It is mentioned in passing at least in bug 436068.
This is a real head-scratcher. I can't pinpoint what causes this or which file installed by dev-ruby/rake makes a difference. Looking at the code in question nothing should, but I can also reproduce this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12d733dbb55780dd082174b43e2d4c13f6a912ab commit 12d733dbb55780dd082174b43e2d4c13f6a912ab Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2024-02-09 09:10:15 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2024-02-09 09:13:50 +0000 dev-ruby/rake: fix tests when rake is not installed Ensure that the test suite uses the local files only, otherwise one of the tests will mysteriously fail when rake is not already installed. Also avoid loading minitest plugins which may break when rake is not present. Closes: https://bugs.gentoo.org/867652 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/rake/rake-13.1.0.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
