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

MutexLincheckTest test failure #3745

Closed
qwwdfsad opened this issue May 8, 2023 · 4 comments
Closed

MutexLincheckTest test failure #3745

qwwdfsad opened this issue May 8, 2023 · 4 comments
Labels

Comments

@qwwdfsad
Copy link
Contributor

qwwdfsad commented May 8, 2023

org.jetbrains.kotlinx.lincheck.LincheckAssertionError: 
= Invalid execution results =
Parallel part:
| unlock(0):  void                  [-,-,1] | tryLock(1): false | tryLock(1): true |
| tryLock(1): true                  [1,-,1] |                   |                  |
| unlock(2):  IllegalStateException [2,1,1] |                   |                  |

---
values in "[..]" brackets indicate the number of completed operations 
in each of the parallel threads seen at the beginning of the current operation
---
org.jetbrains.kotlinx.lincheck.LincheckAssertionError:
= Invalid execution results =
Parallel part:
| unlock(0):  void                  [-,-,1] | tryLock(1): false | tryLock(1): true |
| tryLock(1): true                  [1,-,1] |                   |                  |
| unlock(2):  IllegalStateException [2,1,1] |                   |                  |
---
values in "[..]" brackets indicate the number of completed operations
in each of the parallel threads seen at the beginning of the current operation
@qwwdfsad qwwdfsad added the bug label May 8, 2023
@fvasco
Copy link
Contributor

fvasco commented May 8, 2023

Which version is affected?

@qwwdfsad
Copy link
Contributor Author

qwwdfsad commented May 9, 2023

This one is from 1.7.0;
The probability of reproducing this is not that high though -- new Mutex impl've been in develop for almost a year and this is the first time it has failed. Probably similar to old channels' race

@qwwdfsad
Copy link
Contributor Author

Our initial investigations make us think it's rather a Lincheck bug than Mutex-one.
The trace manifests itself only in stress mode and is, in fact, perfectly linearizable (thus, expected)

@qwwdfsad
Copy link
Contributor Author

This occurred to be a non-linearizability 😢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants