Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple lateinit property has not been initialized exception during analysis #161

Open
EgorkaKulikov opened this issue Nov 28, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@EgorkaKulikov
Copy link
Collaborator

Run ContestEstimator with the following options:

timeLimit = 120
methodFilter = "io.seata.core.protocol.transaction.BranchRegisterRequest.*"
projectFilter = listOf("seata-core-0.5.0")

The following error is found in logs multiple times:

java.lang.InterruptedException: null
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:84) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor.execute(JcTestExecutor.kt:72) ~[main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:177) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:170) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:277) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:271) [main/:?]
	at org.usvm.statistics.collectors.CoveredNewStatesCollector.onStateTerminated(CoveredNewStatesCollector.kt:26) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.statistics.CompositeUMachineObserver.onStateTerminated(UMachineObserver.kt:48) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.UMachine.run(Machine.kt:66) [usvm-core-comp-231128-22.jar:?]
	at org.usvm.machine.JcMachine.analyze(JcMachine.kt:195) [usvm-jvm-comp-231128-22.jar:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:269) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:267) [main/:?]
	at org.utbot.common.ThreadBasedExecutor$invokeWithTimeout$1.invoke(ThreadUtil.kt:75) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at org.utbot.common.ThreadBasedExecutor$ensureThreadIsAlive$1.invoke(ThreadUtil.kt:129) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at org.utbot.common.ThreadBasedExecutor$ensureThreadIsAlive$1.invoke(ThreadUtil.kt:125) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30) [kotlin-stdlib-1.8.22.jar:1.8.22-release-407(1.8.22)]
	
	
	Suppressed: java.lang.IllegalStateException: Unexpected exception kotlin.UninitializedPropertyAccessException: lateinit property rdProcess has not been initialized
		at org.usvm.instrumentation.testcase.descriptor.UTestUnexpectedExecutionBuilder.build(UTestUnexpectedExecutionBuilder.kt:28) ~[usvm-jvm-instrumentation-comp-231128-22.jar:?]
		at org.usvm.instrumentation.executor.UTestConcreteExecutor.executeAsync(UTestConcreteExecutor.kt:69) ~[usvm-jvm-instrumentation-comp-231128-22.jar:?]
		at org.usvm.instrumentation.executor.UTestConcreteExecutor$executeAsync$1.invokeSuspend(UTestConcreteExecutor.kt) ~[usvm-jvm-instrumentation-comp-231128-22.jar:?]
		at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[kotlin-stdlib-1.8.22.jar:1.8.22-release-407(1.8.22)]
		at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:284) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.EventLoopImplBase.shutdown(EventLoop.common.kt:229) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.EventLoop.decrementUseCount(EventLoop.common.kt:114) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.EventLoop.decrementUseCount$default(EventLoop.common.kt:108) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:91) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source) ~[kotlinx-coroutines-core-jvm-1.6.4.jar:?]
		at org.utbot.contest.usvm.jc.JcTestExecutor.execute(JcTestExecutor.kt:72) ~[main/:?]
		at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:177) [main/:?]
		at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:170) [main/:?]
		at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:277) [main/:?]
		at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:271) [main/:?]
		at org.usvm.statistics.collectors.CoveredNewStatesCollector.onStateTerminated(CoveredNewStatesCollector.kt:26) [usvm-core-comp-231128-22.jar:?]
		at org.usvm.statistics.CompositeUMachineObserver.onStateTerminated(UMachineObserver.kt:48) [usvm-core-comp-231128-22.jar:?]
		at org.usvm.UMachine.run(Machine.kt:66) [usvm-core-comp-231128-22.jar:?]
		at org.usvm.machine.JcMachine.analyze(JcMachine.kt:195) [usvm-jvm-comp-231128-22.jar:?]
		at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:269) [main/:?]
		at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:267) [main/:?]
@EgorkaKulikov EgorkaKulikov added the bug Something isn't working label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants