website: tip.golang.org is down #29251
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Soon
This needs action soon. (recent regressions, service outages, unusual time-sensitive situations)
Milestone
Comments
andybons
added
the
NeedsInvestigation
|
Bryan, can you fix this soon? /cc @dmitshur |
bradfitz
added
the
Soon
|
I see no mention of GOCACHE in x/tools or x/net. We're not setting this explicitly anywhere that I can see. |
|
GOCACHE doesn't appear to be set in that container: |
|
Likely related to not being able to detect the home directory, see the
issue I linked
On Fri, Dec 14, 2018 at 14:07 Brad Fitzpatrick ***@***.***> wrote:
I see no mention of GOCACHE in x/tools or x/net. We're not setting this
explicitly anywhere that I can see.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#29251 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAOSI6chk7fLZ6YQ2-TnzKnj20ZCCYHCks5u47CogaJpZM4ZS3IB>
.
--
Kevin Burke
phone: 925.271.7005 | kev.inburke.com
|
|
@kevinburke, ah, great, thanks! |
|
Change https://golang.org/cl/154181 mentions this issue: |
|
I got it kinda back alive, but now the godoc processes are failing after a few minutes with: I added some more debugging, go func() {
// TODO(adg,bradfitz): be smarter about dead processes
if err := cmd.Wait(); err != nil {
log.Printf("process in %v exited: %v (%T)", dir, err, err)
if ee, ok := err.(*exec.ExitError); ok {
if ws, ok := ee.ProcessState.Sys().(syscall.WaitStatus); ok {
log.Printf(" ... ws = %v, stopped=%v, exited=%v, exit=%v", ws, ws.Stopped(), ws.Exited(), ws.ExitStatus())
if ws.Signaled() {
log.Printf(" ... stop signal: %v", ws.StopSignal())
}
}
}
}
}()And now see: What is stop signal -1 !? @ianlancetaylor would be my usual person to ask about that. @bcmills, do you know? |
|
Nevermind. I was misusing StopSignal. I thought it was something else. WaitStatus of 9 just means it got SIGKILLed. |
|
As expected, OOM: Something between Go 1.9 and Go 1.11 uses more memory I guess. Yay. Will increase it a bit for now. |
|
Change https://golang.org/cl/163798 mentions this issue: |
gopherbot
pushed a commit
to golang/playground
that referenced
this issue
Feb 26, 2019
Go 1.12 has been released¹ and should be used, so that it's possible to play with Go programs that rely on Go 1.12-only features. In Go 1.12, build cache is required. Either GOCACHE must be set, or HOME must be set so that GOCACHE can be implicitly deduced. Set HOME and pass it on to the go build invocation inside the compileAndRun function. This fixes the following error, detected by the playground test: 2019/02/26 06:28:44 compile error: build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined The command '/bin/sh -c /app/playground test' returned a non-zero code: 1 This is related to issues golang/go#29243 and golang/go#29251, and the fix in CL 154181. ¹ https://groups.google.com/d/msg/golang-announce/Y1RZqnCKUKY/N9yK5c8iBgAJ Fixes golang/go#30397 Change-Id: I44c5c8928060732f31fd935b114568258c7298c7 Reviewed-on: https://go-review.googlesource.com/c/163798 Reviewed-by: Brad Fitzpatrick <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Fails with this message on all pages:
/cc @bradfitz @bcmills
The text was updated successfully, but these errors were encountered: