kotlinx-lincheck
kotlinx-lincheck copied to clipboard
Kotlin
Framework for testing concurrent data structures
Hi! When I used lincheck to test a (faulty) concurrent hash table i got the following error: ``` Invalid interleaving found, trying to minimize the scenario below: | -------------------------------------- |...
The code is stored [here](https://github.com/de-shyt/kotlin-channels/tree/rendezvous-channel-segment-list-call). The problem appears when `modelCheckingTest()` is run in Debug using Lincheck plugin. ``` WARNING: A Java agent has been loaded dynamically (/Users/Daria.Shutina/.gradle/caches/modules-2/files-2.1/net.bytebuddy/byte-buddy-agent/1.14.12/be4984cb6fd1ef1d11f218a648889dfda44b8a15/byte-buddy-agent-1.14.12.jar) WARNING: If a...
Hi, I have received the following error when using lincheck 2.34 : ``` = Validation function validate has failed = | ------------------------------------- | | Thread 1 | | ------------------------------------- |...
The code is stored [here](https://github.com/de-shyt/kotlin-channels/tree/buffered-channel-expandBuffer-non-determinism). The error can be reproduced by running [`Buffered1ChannelTest`](https://github.com/de-shyt/kotlin-channels/blob/039bd54a84358715795c001e2f96ec0a9e280761/src/test/kotlin/com/deshyt/ChannelsLincheckTest.kt#L23). ``` Non-determinism found. Probably caused by non-deterministic code (WeakHashMap, Object.hashCode, etc). == Reporting the first execution without...
When a suspended coroutine is stored in the array, the Lincheck State Diagram becomes much bigger because of technical stuff 
The code is stored [here](https://github.com/de-shyt/kotlin-channels/tree/buffered-channel-no-plugin-windows). When [`Buffered1ChannelTest`](https://github.com/de-shyt/kotlin-channels/blob/9545a75a192d444751a5185656822252ff6c5423/src/test/kotlin/com/deshyt/ChannelsLincheckTest.kt#L23) is run in Debug, "Lincheck scenario" and "Lincheck state diagram" windows are not shown. I also tried running the code with plugins of...
#353 shows that `FinalFields` can be accessed by concurrent threads. We tried to fix the particular problem with #354. However, how this may happen remains unclear and requires further investigation.