From: Ian Lance Taylor <iant@golang.org>
Date: Wed, 11 Mar 2020 05:11:00 +0000 (-0700)
Subject: time: stop referring to timerproc in comment
X-Git-Tag: go1.15beta1~875
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=85e87f9d81c00d38a196c40f3a93477bc4b3294f;p=gostls13.git

time: stop referring to timerproc in comment

The timerproc function has been removed.

Fixes #37774

Change-Id: Ice5e1d8fec91cd6ee7f032e0d21e8315a26bc6a3
Reviewed-on: https://go-review.googlesource.com/c/go/+/222783
Reviewed-by: Alberto Donizetti <alb.donizetti@gmail.com>
---

diff --git a/src/time/internal_test.go b/src/time/internal_test.go
index 3bca88e2b9..35ce69b228 100644
--- a/src/time/internal_test.go
+++ b/src/time/internal_test.go
@@ -67,12 +67,13 @@ func CheckRuntimeTimerOverflow() {
 		resetTimer(r, 0)
 	}()
 
-	// If the test fails, we will hang here until the timeout in the testing package
-	// fires, which is 10 minutes. It would be nice to catch the problem sooner,
-	// but there is no reliable way to guarantee that timerproc schedules without
-	// doing something involving timerproc itself. Previous failed attempts have
-	// tried calling runtime.Gosched and runtime.GC, but neither is reliable.
-	// So we fall back to hope: We hope we don't hang here.
+	// If the test fails, we will hang here until the timeout in the
+	// testing package fires, which is 10 minutes. It would be nice to
+	// catch the problem sooner, but there is no reliable way to guarantee
+	// that timers are run without doing something involving the scheduler.
+	// Previous failed attempts have tried calling runtime.Gosched and
+	// runtime.GC, but neither is reliable. So we fall back to hope:
+	// We hope we don't hang here.
 	<-t.C
 }