Test suite doctests: RUNNING... doctests: user error (Language.Haskell.GhciWrapper.close: Interpreter exited with an error (ExitFailure 251)) Test suite doctests: FAIL Test suite logged to: dist/test/mailbox-count-0.0.5-doctests.log 1 of 2 test suites (1 of 2 test cases) passed. * ERROR: net-mail/mailbox-count-0.0.5::gentoo failed (test phase): * cabal test failed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-j4_test-20210817-100010 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * /usr/lib/llvm/12 12.0.1 Python 3.9.6 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-1.54.0 * The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit f619796da78d6e1600a6477ba9b990e9282d6b0b Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Aug 21 08:21:31 2021 +0000 2021-08-21 08:21:30 UTC emerge -qpvO net-mail/mailbox-count [ebuild N ] net-mail/mailbox-count-0.0.5 USE="test"
Created attachment 734836 [details] emerge-info.txt
Created attachment 734839 [details] emerge-history.txt
Created attachment 734842 [details] environment
Created attachment 734845 [details] etc.portage.tar.bz2
Created attachment 734848 [details] logs.tar.bz2
Created attachment 734851 [details] net-mail:mailbox-count-0.0.5:20210821-092107.log
Created attachment 734854 [details] temp.tar.bz2
Is this reproducible? As best I can tell, "ExitFailure 251" means that the doctest runner received either a heap overflow or an out-of-memory condition from GHCi, but I'm only guessing from the GHC source code (it's not documented). I've tried rebuilding it a few times with up-to-date ~arch packages and it runs OK here.
Update summary. [something] is used when something refers to an overlay
I just bumped mailbox-count to v0.0.6 and ran the test suite a bunch more times (with an updated toolchain). I really think this was a random issue -- the test suite is pretty predictable.
