Tweet
Hello,
I work in a lab with a few hundred devices and own a Corporate Site License to your software. We have come up with an automated way of running Performance Tests and duplicating the results back onto a server. Long story short we have been able to accomplish everything via automation but we have encountered an interesting issue I wanted to bring up.
When running a full benchmark test including all categories straight from the .exe file everything runs perfectly and all results are recorded properly. However, when automating the task and calling the .exe and subsequent script (using your scripting guidelines/language) via Command Line we receive an Error on the OpenCL test every time. Once we receive the message we cannot manually run it at all unless we completely close the program and reopen it in the traditional way via the .exe manually. Then the OpenCL test functions perfectly fine.
EDIT: We also receive this error after running the software manually then choosing the script via the GUI. OpenCL errors and will not function until PT is reopened.
This is the prompt we receive when running the software:
In summary any time the program is called via command prompt OpenCL Testing throws this Error until it is terminated and re-opened manually.
Thoughts?
I work in a lab with a few hundred devices and own a Corporate Site License to your software. We have come up with an automated way of running Performance Tests and duplicating the results back onto a server. Long story short we have been able to accomplish everything via automation but we have encountered an interesting issue I wanted to bring up.
When running a full benchmark test including all categories straight from the .exe file everything runs perfectly and all results are recorded properly. However, when automating the task and calling the .exe and subsequent script (using your scripting guidelines/language) via Command Line we receive an Error on the OpenCL test every time. Once we receive the message we cannot manually run it at all unless we completely close the program and reopen it in the traditional way via the .exe manually. Then the OpenCL test functions perfectly fine.
EDIT: We also receive this error after running the software manually then choosing the script via the GUI. OpenCL errors and will not function until PT is reopened.
This is the prompt we receive when running the software:
In summary any time the program is called via command prompt OpenCL Testing throws this Error until it is terminated and re-opened manually.
Thoughts?
Comment