From 68b10c2bb8ab95397c70b32ce7c3373eaa6ae9ce Mon Sep 17 00:00:00 2001 From: Ikko Ashimine Date: Mon, 29 Aug 2022 15:48:47 +0000 Subject: [PATCH] internal/trace: fix typo in goroutines.go assosciated -> associated Change-Id: Id1cbbdea12f0239a9e173ece934c18cc9ffcf0f4 GitHub-Last-Rev: 7fea9de6c27b95f91591db4b5bd9023eb80dc522 GitHub-Pull-Request: golang/go#54739 Reviewed-on: https://go-review.googlesource.com/c/go/+/425596 Reviewed-by: Michael Pratt Reviewed-by: Michael Knyszek Auto-Submit: Michael Knyszek TryBot-Result: Gopher Robot Run-TryBot: Michael Knyszek --- src/internal/trace/goroutines.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/internal/trace/goroutines.go b/src/internal/trace/goroutines.go index 5da90e0b6d..796bc8b03c 100644 --- a/src/internal/trace/goroutines.go +++ b/src/internal/trace/goroutines.go @@ -172,7 +172,7 @@ func GoroutineStats(events []*Event) map[uint64]*GDesc { // of the active region. For ease handling of this // case, we create a fake region description with the // task id. This isn't strictly necessary as this - // goroutine may not be assosciated with the task, but + // goroutine may not be associated with the task, but // it can be convenient to see all children created // during a region. if creatorG := gs[ev.G]; creatorG != nil && len(creatorG.gdesc.activeRegions) > 0 { -- 2.50.0