Test for proving Loading rule is not thread safe #2535
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When multiple threads are trying to load rule at the same time even when they refer to different rule set a string representing rule is malformed. It's believed that this is caused by seclang-parser which contains plenty of global variables. To run the test simply enter 'test' directory and run "./unit_tests"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When multiple threads are trying to load rule at the same
time even when they refer to different rule set a string
representing rule is malformed. It's believed that
this is caused by seclang-parser which contains plenty
of global variables.
To run the test simply enter 'test' directory and run
"./unit_tests"