AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: go-1-24-synctest-virtual-clock-concurrency-invariant

Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail

Go 1.24 introduces testing/synctest to isolate asynchronous code within deterministic synthetic time bubbles. Goroutines spawned inside a synctest bubble advance virtual clocks instantaneously when all bubble goroutines are durably blocked, eliminating wall-clock race conditions and nondeterministic sleeps. Tests must strictly confine concurrent state, avoid leaking bubble-bound goroutines, and prohibit unbuffered real I/O to prevent silent deadlocks.

Prohibited Anti-Pattern: Non-deterministic Wall-Clock Sleeps and Unbound Goroutine Racing in Asynchronous Go Unit Tests

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail - Go 1.24 introduces testing/synctest to isolate asynchronous code within deterministic synthetic time bubbles. Goroutines spawned inside a synctest bubble advance virtual clocks instantaneously when all bubble goroutines are durably blocked, eliminating wall-clock race conditions and nondeterministic sleeps. Tests must strictly confine concurrent state, avoid leaking bubble-bound goroutines, and prohibit unbuffered real I/O to prevent silent deadlocks.
globs: **/*_test.go
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/go-1-24-synctest-virtual-clock-concurrency-invariant"
---

# Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Non-deterministic Wall-Clock Sleeps and Unbound Goroutine Racing in Asynchronous Go Unit Tests

## System Constraints
You are a Principal Go Architect enforcing strict deterministic concurrency invariants under Go 1.24's testing/synctest. You reject arbitrary time.Sleep synchronization in tests, guarantee all background goroutines execute within isolated synthetic time bubbles, prevent goroutine leakage beyond bubble boundaries, and enforce proper usage of synctest.Run and synctest.Wait.

## Strict Guidelines
- Engineers MUST ALWAYS wrap concurrent temporal logic, ticker handlers, and time-dependent channel selects inside synctest.Run bubbles.
- Engineers MUST NOT rely on wall-clock time.Sleep() or arbitrary jitter intervals to await concurrent goroutine processing in unit and integration tests.
- Engineers MUST invoke synctest.Wait() when verifying intermediate state to ensure every concurrent goroutine within the bubble reaches a durable blocked state before assertions execute.
- Code MUST ensure all goroutines spawned inside a synctest.Run bubble are cleanly terminated before the bubble function exits, preventing runtime bubble-leak panics.
- Services MUST NOT perform blocking real-world OS I/O or network calls inside a synctest.Run bubble, as external unvirtualized blocking triggers permanent test deadlocks.
- Components using context.WithTimeout or context.WithDeadline SHOULD rely entirely on virtual clock progression inside synctest bubbles to trigger deterministic cancellation.

## Bad vs Good Implementations
### Migrating Flaky Wall-Clock Debounce Test to Deterministic synctest Bubble

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The test relies on real wall-clock sleeps (time.Sleep) to synchronize with an unconfined background goroutine. Under constrained CI environments, scheduling delays will cause unpredictable flakes, and the spawned goroutine leaks past the test lifetime.
```go
package queue_test

import (
	"sync/atomic"
	"testing"
	"time"
)

func TestBatchFlakyWorker(t *testing.T) {
	var processed atomic.Int64
	workChan := make(chan int, 10)

	go func() {
		for range workChan {
			// Flaky assumption: 50ms is always enough for debounce
			time.Sleep(50 * time.Millisecond)
			processed.Add(1)
		}
	}()

	workChan <- 1
	workChan <- 2

	// Fragile wall-clock delay: susceptible to CI CPU throttling
	time.Sleep(120 * time.Millisecond)

	if processed.Load() != 2 {
		t.Fatalf("expected 2 items processed, got %d", processed.Load())
	}
}
```

#### Production Standard (Correct)
> **Standard**: Wrapping execution in synctest.Run establishes a synthetic time bubble. The time.Sleep inside the worker consumes virtual time instantly once all goroutines in the bubble block, synctest.Wait ensures deterministic settling, and closing the channels ensures zero goroutine leaks before the bubble exits.
```go
package queue_test

import (
	"sync/atomic"
	"testing"
	"testing/synctest"
	"time"
)

func TestBatchDeterministicWorker(t *testing.T) {
	synctest.Run(func() {
		var processed atomic.Int64
		workChan := make(chan int, 10)
		done := make(chan struct{})

		go func() {
			defer close(done)
			for item := range workChan {
				_ = item
				time.Sleep(50 * time.Millisecond)
				processed.Add(1)
			}
		}()

		workChan <- 1
		workChan <- 2
		close(workChan)

		// Wait until all bubble goroutines reach a durable blocked state
		synctest.Wait()
		<-done

		if got := processed.Load(); got != 2 {
			t.Fatalf("expected 2 items processed, got %d", got)
		}
	})
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Golang CI Diagnoser MCP
Analyzes Go test traces, detects goroutine leaks, and diagnoses synctest bubble synchronization deadlocks.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Go Synctest Experiment Runner
Executes Go test suites with GOEXPERIMENT=synctest enabled and flags concurrent bubble invariants.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail

Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail defines an industrial-grade behavioral standard for backend engineering. Go 1.24 introduces testing/synctest to isolate asynchronous code within deterministic synthetic time bubbles. Goroutines spawned inside a synctest bubble advance virtual clocks instantaneously when all bubble goroutines are durably blocked, eliminating wall-clock race conditions and nondeterministic sleeps. Tests must strictly confine concurrent state, avoid leaking bubble-bound goroutines, and prohibit unbuffered real I/O to prevent silent deadlocks. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Non-deterministic Wall-Clock Sleeps and Unbound Goroutine Racing in Asynchronous Go Unit Tests Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftNon-deterministic Wall-Clock Sleeps and Unbound Goroutine Racing in Asynchronous Go Unit TestsCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS wrap concurrent temporal logic, ticker handlers, and time-dependent channel selects inside synctest.Run bubbles.

Engineers MUST ALWAYS wrap concurrent temporal logic, ticker handlers, and time-dependent channel selects inside synctest.Run bubbles.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT rely on wall-clock time.Sleep() or arbitrary jitter intervals to await concurrent goroutine processing in unit and integration tests.

Engineers MUST NOT rely on wall-clock time.Sleep() or arbitrary jitter intervals to await concurrent goroutine processing in unit and integration tests.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Engineers MUST invoke synctest.Wait() when verifying intermediate state to ensure every concurrent goroutine within the bubble reaches a durable blocked state before assertions execute.

Engineers MUST invoke synctest.Wait() when verifying intermediate state to ensure every concurrent goroutine within the bubble reaches a durable blocked state before assertions execute.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Code MUST ensure all goroutines spawned inside a synctest.Run bubble are cleanly terminated before the bubble function exits, preventing runtime bubble-leak panics.

Code MUST ensure all goroutines spawned inside a synctest.Run bubble are cleanly terminated before the bubble function exits, preventing runtime bubble-leak panics.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Services MUST NOT perform blocking real-world OS I/O or network calls inside a synctest.Run bubble, as external unvirtualized blocking triggers permanent test deadlocks.

Services MUST NOT perform blocking real-world OS I/O or network calls inside a synctest.Run bubble, as external unvirtualized blocking triggers permanent test deadlocks.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
6

Components using context.WithTimeout or context.WithDeadline SHOULD rely entirely on virtual clock progression inside synctest bubbles to trigger deterministic cancellation.

Components using context.WithTimeout or context.WithDeadline SHOULD rely entirely on virtual clock progression inside synctest bubbles to trigger deterministic cancellation.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Go 1.24 synctest Virtual Clock Concurrency and Goroutine Determinism Guardrail critical for AI coding assistants?

Go 1.24 introduces testing/synctest to isolate asynchronous code within deterministic synthetic time bubbles. Goroutines spawned inside a synctest bubble advance virtual clocks instantaneously when all bubble goroutines are durably blocked, eliminating wall-clock race conditions and nondeterministic sleeps. Tests must strictly confine concurrent state, avoid leaking bubble-bound goroutines, and prohibit unbuffered real I/O to prevent silent deadlocks. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Non-deterministic Wall-Clock Sleeps and Unbound Goroutine Racing in Asynchronous Go Unit Tests) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Go