[golang/go] testing: tests killed with "signal: killed" on go1.26.1 (regression from go1.25.7)

### ROOT CAUSE The issue arises due to a regression in Go 1.26.1 where tests are being killed by the operating system with a "signal: killed" error, typically due to an out-of-memory (OOM) condition. This behavior is a regression from Go 1.25.7, suggesting a change in how the Go toolchain handles test processes or resource allocation. The error indicates the system is killing the process, likely because it exceeded memory limits or encountered resource constraints. ### CODE FIX To address this issue, modify the test code to reduce memory usage and avoid resource exhaustion. Here's a step-by-step solution: 1. **Increase System Memory Limits**: Ensure the system has sufficient memory or adjust resource limits (e.g., via `ulimit` on Linux) to prevent OOM kills. 2. **Optimize Test Memory Usage**: - Reduce large allocations in tests. - Use `defer` to clean up resources promptly. - Avoid loading excessive data in tests. **Example Fix**: ```go // Before (problematic large allocation) func TestLargeData(t *testing.T) { data := make([]byte, 1<<30) // 1GB allocation // ... test logic ... } // After (optimized) func TestLargeData(t *testing.T) { defer func() { // Cleanup code here }() // Use smaller buffers or streaming approach // ... } ``` 3. **Run Tests with Reduced Parallelism**: ```bash go test -parallel 1 -gcflags='-l' ... ``` This limits parallel test execution and enables garbage collection debugging to identify leaks. 4. **Update Go Version**: If the issue persists, downgrade to Go 1.25.7 until the Go team fixes the regression in a newer patch release. **Note**: The Go team may address this in a future release by improving the test runner's memory management. Monitor the Go repository for updates.