Bug 743448

Summary:	dev-python/mpi4py-3.0.3: test_spawn fails
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	Alex Fan <alex.fan.q>
Status:	CONFIRMED ---
Severity:	normal	CC:	dlan, proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://github.com/jsquyres/ompi/pull/4#issuecomment-806897758
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log

Description Agostino Sarubbo gentoo-dev

2020-09-19 05:41:42 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-python/mpi4py-3.0.3 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.

Comment 1 Agostino Sarubbo gentoo-dev

2020-09-19 05:41:45 UTC

Created attachment 661347 [details]
build.log

build log and emerge --info

Comment 2 Agostino Sarubbo gentoo-dev

2020-09-19 05:41:46 UTC

Possible context of error(s):

ld.lld: error: unable to find library -llmpe

Comment 3 Alex Fan archtester

2022-01-09 08:57:02 UTC

This is related to network-sandbox and also likely something in openmpi commspawn. 

I reproduced this, but there is something I don't understand. Running `ebuild mpi4py-3.1.3.ebuild test` directly as root, test_spawn fails exactly the same way. Then if I switch to portage user by `bash --shell=/bin/bash portage` and running the same, this test succeeded. 

Upstream also had this test failure when they were implementing their ci test. Openmpi commspawn is not very stable. Given version 3.0.3 is obsolete and have lots' of tests segfault, I have skipped this test only in 3.1.3 as a workaround. Please test 3.1.3 instead if you would like.