We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@adg, this is why the watcher is crashing in the dev cluster. I now pull the docker logs of the watcher container before nuking it in the coordinator:
Watcher https://go.googlesource.com/gofrontend crashed. Restarting soon. Logs: 2015/06/05 01:06:20 go: cloning https://go.googlesource.com/gofrontend Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: 2015/06/05 01:06:33 go: loading commit log Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: 2015/06/05 01:06:33 go: no parents for initial commit 0ef89c4e8b1f5c66ab6c9a6c307bc153e0f1b0f4[master]("Initial import of gofrontend repository.") Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: 2015/06/05 01:06:33 go: found branch: "master"(Head: 223e7a8250d490fe180418417142e92876715c6d[master]("remove codereview.cfg.") LastSeen: <nil>) Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: 2015/06/05 01:06:33 go: found 1 branches among 1496 commits Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: 2015/06/05 01:06:33 go: sending commit to dashboard: 0ef89c4e8b1f5c66ab6c9a6c307bc153e0f1b0f4[master]("Initial import of gofrontend repository.") Jun 05 01:06:33 farmer.c.go-dashboard-dev.internal coordinator[31128]: postCommit: error: this package already has a first commit; aborting
Note the last line.
Can you fix?
The text was updated successfully, but these errors were encountered:
I need to modify those code anyway as it turns out (gerrit quota issues) so I'll add a workaround for this.
Sorry, something went wrong.
No branches or pull requests
@adg, this is why the watcher is crashing in the dev cluster. I now pull the docker logs of the watcher container before nuking it in the coordinator:
Note the last line.
Can you fix?
The text was updated successfully, but these errors were encountered: