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

Test where zesMemoryGetState & zesFirmwareGetProperties APIs are invoked in threads #81

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

harinik124
Copy link
Contributor

Related to VLCLJ-2289

…ed in parallel

Related to VLCLJ-2289

Signed-off-by: Harini Kumaran <harini.kumaran@intel.com>
std::thread firmwareThreads[numThreads];

for (int i = 0; i < numThreads; i++) {
memoryThreads[i] = std::thread(getMemoryStateTemp, device);
Copy link
Contributor

Choose a reason for hiding this comment

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

@AshwinKumarKulkarni is the test expected to have barrier mechanism in both the functions getMemoryState & getFirmwareProperties ? similar to test GivenValidMemoryAndRasHandlesWhenGettingMemoryGetStateAndRasGetStateFromDifferentThreadsThenExpectBothToReturnSucess

Copy link
Contributor

@AshwinKumarKulkarni AshwinKumarKulkarni left a comment

Choose a reason for hiding this comment

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

  1. move enumerateAPIs to thread body
  2. change get_prop_length ->get_property_length
  3. clean up functions, remove comments/prints
  4. use snake case in CTS to mantain uniformity

…ed in parallel

Related to VLCLJ-2289

Signed-off-by: Harini Kumaran <harini.kumaran@intel.com>
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.

3 participants