Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/build: missing trybot build log #10311

Closed
josharian opened this issue Apr 1, 2015 · 4 comments
Closed

x/build: missing trybot build log #10311

josharian opened this issue Apr 1, 2015 · 4 comments
Assignees
Milestone

Comments

@josharian
Copy link
Contributor

@josharian josharian commented Apr 1, 2015

trybot run: http://farmer.golang.org/try?commit=238dee09

The build log for the openbsd-386-gce56 failure yields a 404. The url looks correct.

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Apr 1, 2015

I don't understand.

That tryrun is over, so the status URL has expired. But the failure log is not a 404.

If I look at the comment it posted to

https://go-review.googlesource.com/#/c/7593/

I see:

This change failed on openbsd-386-gce56:
See https://storage.googleapis.com/go-build-log/238dee09/openbsd-386-gce56_701746e8.log

And that URL works.

What do you want me to do here?

@josharian
Copy link
Contributor Author

@josharian josharian commented Apr 1, 2015

Drat. The status URL expiring has foiled my lazily written bug report.

This change failed on openbsd-386-gce56:
See https://storage.googleapis.com/go-build-log/238dee09/openbsd-386-gce56_701746e8.log
And that URL works.

The farmer.golang.org page had build log link url of the form http://farmer.golang.org/logs?name=plan9-386-gcepartial&rev=fb4b46738cfc0adf4e02781c25603ca16764cdbf&st=0xc208cf1860. That was the URL that was broken.

Given that all the evidence is gone, I guess I'll close this until it happens again.

@josharian josharian closed this Apr 1, 2015
@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Apr 2, 2015

I suppose the more general bug here is that any coordinator URL should either work or redirect somewhere useful.

We could just write out the state to GCS when done (named the same as the URL) and if the state isn't in memory, redirect to the GCS text file URL.

/cc @crawshaw

@bradfitz bradfitz reopened this Apr 2, 2015
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc changed the title build: missing trybot build log x/build: missing trybot build log Apr 14, 2015
@rsc rsc removed the repo-build label Apr 14, 2015
@rsc rsc modified the milestones: Unreleased, Unplanned Apr 14, 2015
@rsc rsc added the Builders label Jun 11, 2015
@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Feb 11, 2017

Closing in favor of broader #13076

@bradfitz bradfitz closed this Feb 11, 2017
@golang golang locked and limited conversation to collaborators Feb 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.