GitHub Actions CI workflow is currently failing

[mdempsky]

E.g., the logs at gh run view --job 5776534338 --log | cat -n show that packages loader and types are currently failing (lines 589 and 48360), but they don't mention any individual tests that actually failed.

What's going on here? Why are the tests failing? Why aren't there additional details logged?

Am I running into resource limits with GitHub Actions? (What are those limits? How do I tell how close I am to hitting them?)

How can I reproduce the failures locally? Why I try running just go test -v -race ./... with either Go 1.17 or Go 1.18, it succeeds.

[mdempsky]

Changing the workflow to use go test -short seems to have worked around the test failures. Leaving this issue open until I have answers to my questions above.

[zephyrtronium]

It looks like amigo/loader.TestStdlib and amigo/types.TestStdlibSSA time out in the CI runner. That may explain why -short fixes them. I don't think the problem is a hard limit in GitHub Actions, since the tests on package types ostensibly run strictly after those on package loader, but I'm not sure why it doesn't print that the tests timed out.

[mdempsky]

I did notice when running the tests locally, they take a lot of memory and started to swap. I wonder if they're getting OOM killed or something on GitHub's runners, and go test doesn't report that?