go: encoding/gob: test frequently failing with "signal: killed" in longtest builder

The encoding/gob test is frequently failing in the longtest builder with output like:

signal: killed
FAIL	encoding/gob	13.202s

(That’s the entire output.)

First example I saw was in https://build.golang.org/log/608043bae4b6ccc72e79f266fd92fa51410517b1, but the failure mode doesn’t obviously relate to the associated CL (https://golang.org/cl/172418).

I haven’t been able to replicate the failure locally so far. I don’t know whether the failure is due to recent changes in the compiler (@mdempsky, @cuonglm) or in cmd/go (myself and @jayconrod).

The transition from passing to failure was partially masked by #31263.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (20 by maintainers)

Commits related to this issue

Most upvoted comments

Some searching suggests that the signal: killed failure message may indicate that the test ran out of memory.

This happened in the past for gob: #28321

I can’t spot anything wrong with escape analysis here. I’m inclined to say encoding/gob’s tests straddle some cliff in the GC sensitive to a few things, and the new escape analysis just tweaked the conditions that it falls over.

@aclements Can I pass this to you to look into for GC?