Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 719688 - dev-libs/openssl fails tests
Summary: dev-libs/openssl fails tests
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
Depends on:
Blocks: CVE-2020-1967
  Show dependency tree
Reported: 2020-04-26 18:12 UTC by Agostino Sarubbo
Modified: 2023-10-17 11:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

build.log.bz2 (build.log.bz2,159.19 KB, application/x-bzip2)
2020-04-26 18:12 UTC, Agostino Sarubbo

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2020-04-26 18:12:30 UTC
This is an auto-filled bug because dev-libs/openssl fails tests.
The issue was originally discovered on ppc, 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.
Comment 1 Agostino Sarubbo gentoo-dev 2020-04-26 18:12:38 UTC
Created attachment 634746 [details]

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2020-04-26 18:14:01 UTC
it looks to be the same of bug 699134 but since this is on ppc and the original is on amd64 and for a different version I created another bug.

The log is with V=1
Comment 3 Georgy Yakovlev archtester gentoo-dev 2020-05-29 18:55:42 UTC
like I answered in the other bug, this test fails due to kernel configuration

we should not block stabilization on it. we'd better update kernel configs on bogsucker and timberdoodle to include those modules, so we can run this test.
Comment 4 Ansers 2023-10-17 11:32:20 UTC
Hey there, fellow bug hunters.

I stumbled upon this rather intriguing conundrum. It appears that dev-libs/openssl is playing hard to get during its tests, particularly on the ppc architecture. But as we all know, mysteries like these can often transcend their initial boundaries and spread their enigmatic influence across other arches. A true test of the dev-libs' mettle!

Now, let's delve into the cryptic details. To tackle this issue, I'd suggest we first take a closer look at that build log and the emerge --info. They might hold some secret clues that could help us unmask this elusive bug. 

In my past escapades with such obstinate bugs, I've often found success by updating system libraries, double-checking compiler flags, or even diving into the depths of environment variables. Every battle-tested developer knows that persistence and a dash of creativity are our most potent weapons in the fight against these cryptic foes. If you're interested in exploring the roles and responsibilities of an automation tester, I recently came across a useful resource on this topic at It can provide add info that can aid us in our quest to conquer this challenge.