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

Discarding based on Trace #416

Open
telser opened this issue Dec 2, 2024 · 0 comments
Open

Discarding based on Trace #416

telser opened this issue Dec 2, 2024 · 0 comments

Comments

@telser
Copy link
Contributor

telser commented Dec 2, 2024

It does not appear that there is any way to discard a possible execution based on the Trace that got us there. This could be very helpful to create assertions based on some part of the execution space.

Full context of what I'm trying to do because there is likely a better way:

I have a networked service that includes some resource locking. I'd like to test with concurrent clients, A and B, such that when A wins the race for the lock and performs task T, the results are X but that when B wins the race and performs task U the results are Y. This would be regardless of interleaving between A and B, but notably the lock primitive is held in the networked service, not between A and B.

In the above I've stated things as if A and B are independent programs, but they really would be separate threads of a single program.

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

No branches or pull requests

1 participant