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

Add mutex stress test #2472

Merged

Conversation

Zzzabiyaka
Copy link
Contributor

@Zzzabiyaka Zzzabiyaka commented Aug 16, 2023

as a part of stress-testing we want to ensure that mutex implementation is working correctly and protecting shared resource to be allocated from other threads when mutex is locked.

This test covers the most common situations that happen when some program uses mutexes like locks from various threads, locks from the same thread etc

If you have any other cases that left uncovered please mention them in the comments

cc @loganek @g0djan @eloparco

@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 3 times, most recently from bd55f8d to c6d48bf Compare August 21, 2023 15:02
@Zzzabiyaka Zzzabiyaka changed the title [WIP] Add mutex stress test to WAMR Add mutex stress test to WAMR Aug 21, 2023
@Zzzabiyaka Zzzabiyaka marked this pull request as ready for review August 21, 2023 15:06
@Zzzabiyaka Zzzabiyaka changed the title Add mutex stress test to WAMR Add mutex stress test Aug 21, 2023
@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 7 times, most recently from 796603d to 9538d42 Compare August 21, 2023 21:03
@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 2 times, most recently from 7edf4b2 to de50d6e Compare August 22, 2023 10:03
@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 9 times, most recently from 248e53a to d78628c Compare August 24, 2023 09:59
@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 4 times, most recently from 3098b47 to 08adea1 Compare August 24, 2023 15:04
Copy link
Collaborator

@loganek loganek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@Zzzabiyaka Zzzabiyaka force-pushed the makslit/mutex_stress_test branch 5 times, most recently from 4e4c64e to 9e13126 Compare August 29, 2023 13:12
@lum1n0us
Copy link
Collaborator

LGTM

@wenyongh wenyongh merged commit 411b903 into bytecodealliance:main Aug 30, 2023
611 checks passed
victoryang00 pushed a commit to victoryang00/wamr-aot-gc-checkpoint-restore that referenced this pull request May 27, 2024
As a part of stress-testing we want to ensure that mutex implementation is working
correctly and protecting shared resource to be allocated from other threads when
mutex is locked.

This test covers the most common situations that happen when some program uses
mutexes like locks from various threads, locks from the same thread etc.
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

Successfully merging this pull request may close these issues.

5 participants