In the CLI when running a scripted loop of tests, if the Virtual Users are still active from a previous test and vudestroy has not been able to close the thread running the vurun command will error with the message:
Error: can't read "threadscreated(0)": no such variable
Although this message has no negative impact, it should be improved to show that the error came from the vurun command.
In most cases this can be resolved by moving the CLI keepalive_margin setting.
Example of the current output is as follows:
Vuser 1:TEST RESULT : System achieved 13869 NOPM from 32266 MariaDB TPM
Vuser 1:Gathering timing data from Active Virtual Users...
32928 MariaDB tpm
Vuser 2:FINISHED SUCCESS
Vuser 1:Calculating timings...
Vuser 1:Writing timing data to /tmp/hdbxtprofile.log
Vuser 1:Starting purge: history list length 10181
1428 MariaDB tpm
doing vudestory
Transaction Counter thread running with threadid:tid0x7fd6ef7ee700
Stopping Transaction Counter
Virtual Users remain running in background or shutting down, retry
Transaction Counter Started
doing vuset
Error: Virtual Users exist, destroy with vudestroy before changing settings
doing vucreate
Error: Virtual Users exist, destroy with vudestroy before creating
Transaction Counter thread running with threadid:tid0x7fd6ef7ee700
doing vurun
Virtual Users still active in background
Wait for Virtual Users to finish?
Enter yes or no: replied yes
Error: can't read "threadscreated(0)": no such variable
doing vudestory
Transaction Counter thread running with threadid:tid0x7fd6ef7ee700
Stopping Transaction Counter
0 MariaDB tpm
Virtual Users remain running in background or shutting down, retry
Transaction Counter Started
doing vuset
Error: Virtual Users exist, destroy with vudestroy before changing settings
doing vucreate
Error: Virtual Users exist, destroy with vudestroy before creating
Transaction Counter thread running with threadid:tid0x7fd6ef7ee700
doing vurun
Virtual Users still active in background
Wait for Virtual Users to finish?
Enter yes or no: replied yes
Error: can't read "threadscreated(0)": no such variable
doing vudestory
Transaction Counter thread running with threadid:tid0x7fd6ef7ee700
Stopping Transaction Counter
Virtual Users remain running in background or shutting down, retry
In the CLI when running a scripted loop of tests, if the Virtual Users are still active from a previous test and vudestroy has not been able to close the thread running the vurun command will error with the message:
Error: can't read "threadscreated(0)": no such variableAlthough this message has no negative impact, it should be improved to show that the error came from the vurun command.
In most cases this can be resolved by moving the CLI keepalive_margin setting.
Example of the current output is as follows: