Eliminate VU races, unify execution loop, remove cpu check loop

[skudasov]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes introduced are aimed at enhancing thread safety and error handling within the virtual user (VU) management and paced call functionality of a load testing tool. Specifically, ensuring mutual exclusion when accessing shared resources and improving robustness in the rate-limited call execution.

What

• wasp/wasp.go
  • In the runExecuteLoop function, mutual exclusion locks (currentSegmentMu.Lock() and currentSegmentMu.Unlock()) are added around the code block where virtual users (g.vus) are appended to the slice. This ensures thread safety when modifying the shared g.vus slice.
  • In the processSegment function, similar mutual exclusion locks are added around sections where the g.vus slice is either trimmed or appended to, depending on the new virtual user count. This change prevents concurrent write issues.
  • The pacedCall function is modified to include a preliminary nil check on the rate limiter (g.rl) reference before attempting to invoke its Take() method. This addition prevents potential nil pointer dereferences, enhancing the function's robustness.

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
15.4% Duplication on New Code (required ≤ 5%)

See analysis details on SonarQube