I have test failures, is master the correct branch to build from?
David Holmes
david.holmes at oracle.com
Wed May 12 06:58:16 UTC 2021
Hi Luke,
On 12/05/2021 2:00 pm, Luke B wrote:
> Hi,
>
> I did not run --with-gtest adding that has resulted in the number of
> failures dropping to 1 :D
Good result!
> The failure is in:
> serviceability/sa/ClhsdbFindPC.java#id3: Test the clhsdb 'findpc' command
> w/o Xcomp on core
Known issue. Test fails intermittently on some Linuxes:
https://bugs.openjdk.java.net/browse/JDK-8263242
Cheers,
David
-----
> Here is a section of the output from the test:
>
> stdout: [ + findpc 0x00007f3ddfa14548
> Address 0x00007f3ddfa14548: In unknown location
> ];
> stderr: [ + findpc 0x00007f3ddfa14548
> Address 0x00007f3ddfa14548: In unknown location
> ]
> exitValue = -1
>
> java.lang.RuntimeException: Test ERROR java.lang.RuntimeException:
> 'Address 0x00007f3ddfa14548: .*MaxJNILocalCapacity' missing from
> stdout/stderr
>
> at ClhsdbFindPC.testFindPC(ClhsdbFindPC.java:283)
> at ClhsdbFindPC.main(ClhsdbFindPC.java:305)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
> at java.base/java.lang.Thread.run(Thread.java:831)
> Caused by: java.lang.RuntimeException: 'Address 0x00007f3ddfa14548:
> .*MaxJNILocalCapacity' missing from stdout/stderr
>
> at jdk.test.lib.process.OutputAnalyzer.shouldMatch(OutputAnalyzer.java:325)
> at ClhsdbLauncher.runCmd(ClhsdbLauncher.java:166)
> at ClhsdbLauncher.runOnCore(ClhsdbLauncher.java:225)
> at ClhsdbFindPC.runTest(ClhsdbFindPC.java:295)
> at ClhsdbFindPC.testFindPC(ClhsdbFindPC.java:278)
> ... 7 more
>
> JavaTest Message: Test threw exception: java.lang.RuntimeException:
> Test ERROR java.lang.RuntimeException: 'Address 0x00007f3ddfa14548:
> .*MaxJNILocalCapacity' missing from stdout/stderr
>
> JavaTest Message: shutting down test
>
> STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test
> ERROR java.lang.RuntimeException: 'Address 0x00007f3ddfa14548:
> .*MaxJNILocalCapacity' missing from stdout/stderr
>
> The complete output is available at: https://pastebin.com/kz7DsHZU
>
> many thanks,
>
> Luke
>
> On Tue, May 11, 2021 at 9:24 PM Thomas Stüfe <thomas.stuefe at gmail.com>
> wrote:
>
>>
>> On Tue, May 11, 2021 at 11:06 AM Aleksey Shipilev <shade at redhat.com>
>> wrote:
>>
>>> On 5/11/21 11:00 AM, Luke B wrote:
>>>> Looking in the report.html for the hotspot tests I see:
>>>> "native" failed 7 tests and "bug8251158 native" failed 2 tests.
>>>
>>> Please show the *names* of the failing tests, i.e. their file paths. And
>>> the gist of the failing
>>> test output (i.e. console output of "make run-test-tier1").
>>>
>>> "bug8251158" suggests these are gtest tests?
>>>
>>> $ ack 8251158 test/
>>> test/hotspot/jtreg/runtime/Metaspace/elastic/TestMetaspaceAllocation.java
>>> 28: * @bug 8251158
>>> 46: * @bug 8251158
>>>
>>> test/hotspot/jtreg/gtest/MetaspaceGtests.java
>>> 33: * @bug 8251158
>>> 44: * @bug 8251158
>>> 57: * @bug 8251158
>>> 68: * @bug 8251158
>>>
>>> So this might suggest you have a problem with google-test. tier1 passes
>>> well with
>>> googletest-release-1.8.1 for me.
>>>
>>>
>> @Luke: did you build with --with-gtest? That is needed for these tests.
>>
>> Cheers, Thomas
>>
>>
>>>> Is this expected, am I building the wrong branch? If not do I need to
>>>> install something to get those tests passing?
>>>
>>> tier1 is supposed to pass everywhere.
>>>
>>>> Should I be applying a ProblemList.txt, if so which one and how should
>>> that
>>>> be run? Perhaps I need to call jtreg directly rather than via make?
>>>
>>> jtreg would hook up the default ProblemList.txt itself, you don't need to
>>> do anything else.
>>>
>>> --
>>> Thanks,
>>> -Aleksey
>>>
>>>
More information about the hotspot-dev
mailing list