Skip to content

jmockit 1.50 introduces a concurrency issue in ExecutingTest.java it seems #752

@craftey

Description

@craftey

Hello,

I have a test that runs a method in a forkjoinpool of size 1000. Sometimes the test succeeds. But often it fails with:

Caused by: java.util.ConcurrentModificationException
	at mockit.internal.expectations.state.ExecutingTest.isInjectableMock(ExecutingTest.java:142)
	at mockit.internal.expectations.state.ExecutingTest.isUnmockedInstance(ExecutingTest.java:145)
	at my.CommonProperties.getClientType(CommonProperties.java)
       ...

CommonProperties is a POJO that I inject in the tested class.

With v1.49 this exception does never happen.

Cheers,
Craftey

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions