You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2020/06/10 22:58:00 UTC

[jira] [Commented] (KAFKA-7743) "pure virtual method called" error message thrown for unit tests which PASS

    [ https://issues.apache.org/jira/browse/KAFKA-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132774#comment-17132774 ] 

Matthias J. Sax commented on KAFKA-7743:
----------------------------------------

[~stamba] Is this issue resolve in newer versions? We did change the used RocksDB version.

> "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
(v8.3.4#803005)