From 2731f408fc6bcc11e2c1b0b2ce52c6fbc691b4e2 Mon Sep 17 00:00:00 2001 From: testiPyqejCa Date: Thu, 10 Oct 2024 16:31:38 +0800 Subject: [PATCH] Add "Download-build-farm-failed-logs-and-debugging" --- ...load-build-farm-failed-logs-and-debugging.-.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 Download-build-farm-failed-logs-and-debugging.-.md diff --git a/Download-build-farm-failed-logs-and-debugging.-.md b/Download-build-farm-failed-logs-and-debugging.-.md new file mode 100644 index 0000000..df8aff3 --- /dev/null +++ b/Download-build-farm-failed-logs-and-debugging.-.md @@ -0,0 +1,15 @@ +The Go project has all build failed logs storage at GCE, which you can access by the [dashboard](https://build.golang.org/). + +You can download all the failed logs by `fetchlogs`. + +Download `fetchlogs` by `go get golang.org/x/build/cmd/fetchlogs` + +`fetchlogs` only download 300 lastest failed logs by default, which is not enough for "mystery"/"flaky" bugs. +`fetchlogs -n ` + +You may also want to take a look at +`github.com/aclements/go-misc/greplogs`. It's a useful tool by Austin +to run grep over logs fetched by fetchlogs. + +Also `github.com/aclements/findflakes` can make some guesses as to when a +flaky test started failing. \ No newline at end of file