plumbing/transport/ssh/common_test.go:178

• The TestIssue70Suite test modifies the global DefaultAuthBuilder variable (lines 159-161) and then relies on a defer to restore it. However, since the test is marked to run in parallel (line 158), other tests could be accessing DefaultAuthBuilder concurrently, leading to data races or unexpected behavior. Tests that modify global state should not run in parallel with other tests that might use that same global state.
  utils/trace/trace_test.go:85
• The trace tests modify global state through SetLogger and SetTarget functions, but SetLogger (line 50-52 of trace.go) directly assigns to the global logger variable without synchronization, while SetTarget uses atomic operations. When tests run in parallel, concurrent calls to SetLogger could cause data races. The tests should either not run in parallel, or the trace package needs to be refactored to be thread-safe for logger changes.
  plumbing/hash/hash_test.go:55
• The TestRegisterHash test and its subtests modify the global algos map through RegisterHash calls. Even though there's a defer reset() at the parent test level, the subtests run in parallel (line 44) and can interfere with each other by registering different hash implementations concurrently. The global map is not protected by any synchronization mechanism, which could lead to data races when tests run in parallel.
  plumbing/hash/hash_test.go:107
• The TestSha1Collision test and its subtests also modify the global algos map through RegisterHash calls (line 80). With subtests running in parallel (line 87), concurrent modifications to the global map can cause data races. The defer reset() only protects against interference with other top-level tests, not between parallel subtests.