You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GO_TEST_TIMEOUT_SCALE is usually not appropriate to use directly, since users themselves generally won't set it. (Its main effect is to extend the timeout that the builder sets via the -test.timeout flag.)
If the hard-coded timeout is too short, I wonder if it would make sense to remove it entirely and just check whether the test livelocks..? (It was loosened once already for #41015.)
TestPreemptionAfterSyscall and runtime/pprof no longer fail, after the builder was upgraded.
Hardware wise, it's an ARM Cortex A7 -> Cortex A53 (in 32bit mode).
FreeBSD 13.0 -> 13.1 and also switched from the default SCHED_ULE to SCHED_4BSD.
Reviewed-by: Bryan Mills <firstname.lastname@example.org>
Reviewed-by: Dmitri Shuralyov <email@example.com>
Run-TryBot: Dmitri Shuralyov <firstname.lastname@example.org>
TryBot-Result: Gopher Robot <email@example.com>
Auto-Submit: Dmitri Shuralyov <firstname.lastname@example.org>