[ https://issues.apache.org/jira/browse/KAFKA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731770#comment-16731770 ]
Sarvesh Tamba commented on KAFKA-7743: -------------------------------------- [~mjsax] any inputs on this? This is blocking our work on validating kafka on SLES12-SP2. Any guidance would be highly appreciated. > "pure virtual method called" error message thrown for unit tests which PASS > --------------------------------------------------------------------------- > > Key: KAFKA-7743 > URL: https://issues.apache.org/jira/browse/KAFKA-7743 > Project: Kafka > Issue Type: Bug > Components: streams, unit tests > Affects Versions: 2.0.0, 2.0.1, 2.1.0 > Reporter: Sarvesh Tamba > Priority: Critical > > Observing the following messages intermittently for a few random unit tests, > though the status for each of them is PASSED:- > *"pure virtual method called* > *terminate called without an active exception"* > Some of the unit tests throwing above messages are, besides others:- > org.apache.kafka.streams.kstream.internals.KTableImplTest > > shouldThrowNullPointerOnTransformValuesWithKeyWhenMaterializedIsNull PASSED > org.apache.kafka.streams.processor.internals.GlobalStreamThreadTest > > shouldThrowStreamsExceptionOnStartupIfThereIsAStreamsException PASSED > org.apache.kafka.streams.state.internals.CachingSessionStoreTest > > shouldNotForwardChangedValuesDuringFlushWhenSendOldValuesDisabled PASSED > org.apache.kafka.streams.processor.internals.StoreChangelogReaderTest > > shouldCompleteImmediatelyWhenEndOffsetIs0 PASSED > org.apache.kafka.streams.kstream.internals.KStreamKStreamJoinTest > testJoin > PASSED > org.apache.kafka.streams.kstream.internals.KTableFilterTest > > testTypeVariance PASSED > org.apache.kafka.streams.kstream.internals.KTableKTableInnerJoinTest > > testNotSendingOldValues PASSED > org.apache.kafka.streams.processor.internals.GlobalStreamThreadTest > > shouldThrowStreamsExceptionOnStartupIfThereIsAStreamsException PASSED > org.apache.kafka.streams.processor.DefaultPartitionGrouperTest > > shouldComputeGroupingForTwoGroups PASSED > org.apache.kafka.streams.state.internals.RocksDBWindowStoreTest > > shouldFetchAndIterateOverExactKeys PASSED > org.apache.kafka.streams.state.internals.FilteredCacheIteratorTest > > shouldFilterEntriesNotMatchingHasNextCondition PASSED > org.apache.kafka.streams.state.internals.GlobalStateStoreProviderTest > > shouldThrowExceptionIfStoreIsntOpen PASSED > This probably causes the 'gradle unitTest' command to fail during cleanup > time with final status as FAILED and the following message:- > "Process 'Gradle Test Executor 16' finished with non-zero exit value 134" > This intermittent/random error is not seen when final unit test suite status > is "BUILD SUCCESSFUL". > Reproducing "pure virtual method" issue is extremely hard, since it happens > intermittently and for any random unit test(not the same unit test will fail > next time). The ones noted above were some of the failing unit tests > observed. Note that the status next to the test shows PASSED(is this correct > or misleading?). -- This message was sent by Atlassian JIRA (v7.6.3#76005)