This is an auto-filled bug because dev-python/ndg-httpsclient fails tests.
The issue was originally discovered on amd64, but it may be reproducible on other arches as well.
If you think that a different summary clarifies the issue better, feel free to change it.
Attached build log and emerge --info.
Created attachment 635834 [details]
build log and emerge --info
Am I missing something or do system commands such as mkdir segfault on you?
mkdir works for me from cli. I am able to emerge everything else that is doing a massive usage of mkdir. I don't know why this issue happened.
Created attachment 644042 [details]
On arm64, segfaults on a different line.
Tests pass outside of sandbox:
FAKETIME="@2019-12-01 12:00:00" LD_PRELOAD="libfaketime.so" python -m unittest discover -v
Could you try removing libfaketime and trying again?
The bug has been closed via the following commit(s):
Author: Sam James <firstname.lastname@example.org>
AuthorDate: 2020-07-24 16:32:17 +0000
Commit: Sam James <email@example.com>
CommitDate: 2020-07-24 17:09:07 +0000
dev-python/ndg-httpsclient: fix tests with upstream patch
This isn't an ideal fix. The problem was that upstream's
bundled certs had expired. Now we have a newer set provided and
the necessary keys.
We may want to use the keys to generate our own certificates
if upstream are inactive in future.
Note that we drop the libfaketime dependency because:
1) it's no longer necessary;
2) it was causing segfaults in Portage's sandbox sometimes.
Package-Manager: Portage-3.0.0, Repoman-2.3.23
Signed-off-by: Sam James <firstname.lastname@example.org>
...ndg-httpsclient-0.5.1-expiration-test-fix.patch | 277 +++++++++++++++++++++
.../ndg-httpsclient/ndg-httpsclient-0.5.1.ebuild | 9 +-
2 files changed, 281 insertions(+), 5 deletions(-)