Description
In L1 test, Randomly test cases are failing
pthread_kill() is failing in stopRuncMonitorThread() which is calling from destructor.
Sometime runcMonitorThread() is starting late, with in the time, if dobbymanager object is deleted, pthread_kill() is failing because the thread is not yet started.
solution: Need to be add the semaphore handling to avoid this sync issue.
Expected Behaviour
pthread_kill() should not fail and destructor should happened without any issues
Actual Behaviour
pthread_kill() is failing and exit from the process
If including the Dobby log, please ensure Dobby has been started with the verbose flag (-v)
Steps to Reproduce
Run the L1 test in github workflow and randomly this issue will reproduce
Platform/Environment
- Run the L1 test in github workflow
Description
In L1 test, Randomly test cases are failing
pthread_kill() is failing in stopRuncMonitorThread() which is calling from destructor.
Sometime runcMonitorThread() is starting late, with in the time, if dobbymanager object is deleted, pthread_kill() is failing because the thread is not yet started.
solution: Need to be add the semaphore handling to avoid this sync issue.
Expected Behaviour
pthread_kill() should not fail and destructor should happened without any issues
Actual Behaviour
pthread_kill() is failing and exit from the process
If including the Dobby log, please ensure Dobby has been started with the verbose flag (
-v)Steps to Reproduce
Run the L1 test in github workflow and randomly this issue will reproduce
Platform/Environment