Santiago Vila <sanv...@unex.es> writes:
> On Sun, Jan 06, 2019 at 12:16:21AM +0800, Yanhao Mo wrote: > >> I cannnot reproduce this problem in my pbuilder environment. >> Could you please help reverify if this problem still exists? > > Note: I reported this because it failed for me once and I saw that it also > failed in reproducible-builds. > > I've now triggered a rebuild on reproducible-builds in all architectures. > > In a while you can see the results here: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hotspot.html > > If all of them build ok, you should probably ask for a retry here: > > https://buildd.debian.org/status/package.php?p=hotspot > > If not, we will see what can we do. > > Thanks. Hmm, the reproducible building is still failed. And I still cannot reproduce the error. Accordding to the error message: > XPASS : TestKallsyms::testProc() 'kallsyms.parseMapping(path)' returned TRUE > unexpectedly. () > Loc: > [/<<BUILDDIR>>/hotspot-1.1.0+git20180816/3rdparty/perfparser/tests/auto/kallsyms/tst_kallsyms.cpp(138)] > QDEBUG : TestKallsyms::testParseErrors() "Mapping is empty." > QDEBUG : TestKallsyms::testParseErrors() "Invalid address: this" > QDEBUG : TestKallsyms::testParseErrors() "No such file or directory" I guess that because the build environments used by tests.reproducible-builds.org dosen't have a normal /proc/kallsyms file. Or maybe it doesn't have such file at all. Could you please help verify that? Very appreciated. And if what I'm guessing is true for the /proc/kallsyms file. Then what operations am I excepted to take? Should I just disable the specific testcase?
