321fe744f3
This CL changes the last line displayed after the program was run to display more details on what happened. If the program cannot be built, the last message is "Go build failed". If the program has tests, the last message is "All tests passed" in case of success. Otherwise it is "N tests failed". If the program has exited with non-zero code, the exit message is postfixed with the code. This CL adds output for timed out programs. This CL is prerequisite for the backend change in CL 141478. Dockerfile in playground repo has to be updated to include this CL. Updates golang/go#10590 Updates golang/go#25454 Change-Id: Ie0a51b0729c574d2508a4a1b89f629def1d79fd6 Reviewed-on: https://go-review.googlesource.com/c/141477 Reviewed-by: Andrew Bonventre <andybons@golang.org>
godoc
This directory contains most of the code for running a godoc server. The executable lives at golang.org/x/tools/cmd/godoc.
Development mode
In production, CSS/JS/template assets need to be compiled into the godoc binary. It can be tedious to recompile assets every time, but you can pass a flag to load CSS/JS/templates from disk every time a page loads:
godoc -templates=$GOPATH/src/golang.org/x/tools/godoc/static -http=:6060
Recompiling static assets
The files that live at static/style.css, static/jquery.js and so on are not
present in the final binary. They are placed into static/static.go by running
go generate. So to compile a change and test it in your browser:
-
Make changes to e.g.
static/style.css. -
Run
go generate golang.org/x/tools/godoc/staticsostatic/static.gopicks up the change. -
Run
go install golang.org/x/tools/cmd/godocso the compiledgodocbinary picks up the change. -
Run
godoc -http=:6060and view your changes in the browser. You may need to disable your browser's cache to avoid reloading a stale file.