testing: tests killed with "signal: killed" on go1.26.1 (regression from go1.25.7)

[kuba1stach]

Go version

1.26.1 linux-amd64

Output of go env in your module/workspace:

AR='ar'
CC='gcc'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_ENABLED='1'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
CXX='g++'
GCCGO='gccgo'
GO111MODULE=''
GOAMD64='v1'
GOARCH='amd64'
GOAUTH='netrc'
GOBIN=''
GOCACHE='/home/jakub/.cache/go-build'
GOCACHEPROG=''
GODEBUG=''
GOENV='/home/jakub/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFIPS140='off'
GOFLAGS=''
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build227149699=/tmp/go-build -gno-record-gcc-switches'
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMOD='/home/jakub/Repos/hello/go.mod'
GOMODCACHE='/home/jakub/go/pkg/mod'
GONOPROXY='internal.company'
GONOSUMDB='internal.company'
GOOS='linux'
GOPATH='/home/jakub/go'
GOPRIVATE='internal.company'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/jakub/.config/go/telemetry'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.26.1'
GOWORK=''
PKG_CONFIG='pkg-config'

What did you do?

1. Install go1.26.1
2. Update go version in go.mod
3. Run go mod tidy
4. Run go test ./... -count=1
   There should be at least a few packages to run tests for all of them at once. But packages can be very simple. It happens only for some people. In my organization some people have this problem and some don't.

Example of packages that failed:

package utils

func IsEven(n int) bool {
	return n%2 == 0
}

func IsOdd(n int) bool {
	return n%2 != 0
}

func Max(a, b int) int {
	if a > b {
		return a
	}
	return b
}

const Version = "1.0.0"

package utils

import (
	"testing"

	"github.com/stretchr/testify/assert"
)

func Test_IsEven(t *testing.T) {
	assert.True(t, IsEven(4), "4 should be even")
	assert.False(t, IsEven(3), "3 should not be even")
}

func Test_IsOdd(t *testing.T) {
	assert.True(t, IsOdd(3), "3 should be odd")
	assert.False(t, IsOdd(4), "4 should not be odd")
}

func Test_Max(t *testing.T) {
	assert.Equal(t, 5, Max(3, 5), "Max should return 5")
}

or

package calc

func Square(n int) int {
	return n * n
}

func Cube(n int) int {
	return n * n * n
}

func Abs(n int) int {
	if n < 0 {
		return -n
	}
	return n
}

const DefaultBase = 10

package calc

import (
	"testing"

	"github.com/stretchr/testify/assert"
)

func Test_Square(t *testing.T) {
	assert.Equal(t, 9, Square(3), "Square of 3 should be 9")
}

func Test_Cube(t *testing.T) {
	assert.Equal(t, 27, Cube(3), "Cube of 3 should be 27")
}

func Test_Abs(t *testing.T) {
	assert.Equal(t, 5, Abs(-5), "Abs of -5 should be 5")
}

What did you see happen?

Most test packages fail with "signal: killed":

• example/hello passes
• example/hello/calc: FAIL (signal: killed)
• example/hello/converters: FAIL (signal: killed)
• example/hello/formatters: FAIL (signal: killed)
• example/hello/helpers: FAIL (signal: killed)
• example/hello/math: FAIL (signal: killed)
• example/hello/parsers: FAIL (signal: killed)
• example/hello/processors: FAIL (signal: killed)
• example/hello/strings: FAIL (signal: killed)
• example/hello/utils: FAIL (signal: killed)
• example/hello/validators passes

Differences between versions:

jakub@JS-DTP0661:~/Repos/hello$ go version
go version go1.25.7 linux/amd64
jakub@JS-DTP0661:~/Repos/hello$ go test ./... -count=1
ok      example/hello   0.306s
ok      example/hello/calc      0.486s
ok      example/hello/converters        0.719s
ok      example/hello/formatters        0.483s
ok      example/hello/helpers   0.306s
ok      example/hello/math      0.478s
ok      example/hello/parsers   0.719s
ok      example/hello/processors        0.719s
ok      example/hello/strings   0.720s
ok      example/hello/utils     0.719s
ok      example/hello/validators        0.481s
jakub@JS-DTP0661:~/Repos/hello$ go version
go version go1.26.1 linux/amd64
jakub@JS-DTP0661:~/Repos/hello$ go mod tidy
jakub@JS-DTP0661:~/Repos/hello$ go test ./... -count=1
ok      example/hello   0.030s
signal: killed
FAIL    example/hello/calc      0.262s
signal: killed
FAIL    example/hello/converters        0.309s
signal: killed
FAIL    example/hello/formatters        0.309s
signal: killed
FAIL    example/hello/helpers   0.699s
signal: killed
FAIL    example/hello/math      1.247s
signal: killed
FAIL    example/hello/parsers   0.968s
signal: killed
FAIL    example/hello/processors        0.670s
signal: killed
FAIL    example/hello/strings   0.672s
signal: killed
FAIL    example/hello/utils     1.294s
ok      example/hello/validators        0.681s
FAIL

What did you expect to see?

• go1.25.7: All tests pass
• go1.26.1: All tests pass

[Jorropo]

It works for me.

Do you know what is sending the KILL signal ?
Are you running out of memory on 1.26.1 and systemd-oomd is killing your test processes by chance ?

[kuba1stach]

Checked system logs to determine if SIGKILL is from OOM killer:

• systemd-oomd logs show no process terminations
• No kernel OOM messages in dmesg
• systemd-oomd memory usage is minimal (2.6-2.9M peak)

[Jorropo]

Can you figure out which process is sending the signal ?

[gabyhelp]

Related Issues

• simd/archsimd: tests SIGILL on unsupported cpus, missing feature check #76866 (closed)
• cmd/compile/internal/amd64: TestGoAMD64v1 test failures (on some machines) #77674 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[kuba1stach]

It is caused by Cortex, not update of golang.