runtime: remove arbitrary GOARCH constraints in finalizer tests

These tests were only run on GOARCH=amd64, but the rationale given in
CL 11858043 was GC precision on 32-bit platforms. Today, we have far
more 64-bit platforms than just amd64, and I believe that GC precision
on 32-bit platforms has been substantially improved as well.
The GOARCH restriction seems unnecessary.

Updates #57166.
Updates #5368.

Change-Id: I45c608b6fa721012792c96d4ed94a6d772b90210
Reviewed-on: https://go-review.googlesource.com/c/go/+/456120
Run-TryBot: Bryan Mills <bcmills@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Auto-Submit: Bryan Mills <bcmills@google.com>
Reviewed-by: Austin Clements <austin@google.com>
This commit is contained in:
Bryan C. Mills 2022-12-08 08:44:51 -05:00 committed by Gopher Robot
parent caf8fb1e82
commit fbf14ae166
1 changed files with 0 additions and 7 deletions

View File

@ -21,10 +21,6 @@ type Tinter interface {
}
func TestFinalizerType(t *testing.T) {
if runtime.GOARCH != "amd64" {
t.Skipf("Skipping on non-amd64 machine")
}
ch := make(chan bool, 10)
finalize := func(x *int) {
if *x != 97531 {
@ -82,9 +78,6 @@ type bigValue struct {
}
func TestFinalizerInterfaceBig(t *testing.T) {
if runtime.GOARCH != "amd64" {
t.Skipf("Skipping on non-amd64 machine")
}
ch := make(chan bool)
done := make(chan bool, 1)
go func() {