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: host-plan9-386-0intro builder is stuck #37926

Closed
bcmills opened this issue Mar 18, 2020 · 3 comments
Closed

x/build: host-plan9-386-0intro builder is stuck #37926

bcmills opened this issue Mar 18, 2020 · 3 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Mar 18, 2020

My SlowBot run on https://farmer.golang.org/try?commit=497ccd63 has been stuck for 13 hours now

https://farmer.golang.org/ shows:

  • host-plan9-386-0intro: 24 waiting (oldest 37h51m38s, newest 12h59m16s, progress 37h4m44s)
    • try: 1 (oldest 12h59m16s, newest 12h59m16s)
plan9-386-0intro rev 7ec4adbc; running; http://gnot reverse peer gnot/136.243.175.38:58736 for host type host-plan9-386-0intro, 37h18m53s ago
...
  2020-03-17T01:40:50Z finish_write_go_src_tar after 7.54s
  2020-03-17T01:40:50Z make_and_test 
  2020-03-17T01:40:50Z make src/make.rc
 +133476.0s (now)

CC @dmitshur @toothrot @cagedmantis @andybons

@bcmills bcmills added this to the Unreleased milestone Mar 18, 2020
@dmitshur

This comment has been minimized.

Copy link
Member

@dmitshur dmitshur commented Mar 18, 2020

The SlowBot run is stuck in waiting_on_machine state, meaning it's waiting for a builder to become available and get scheduled to run that build.

There's only one plan9-386-0intro reverse builder, and it's currently trying to build commit 7ec4adb. It has gotten this far in the last 37 hours:

  builder: plan9-386-0intro
      rev: 7ec4adbc919df7dbd549ccc71a2e17d8a0bafe4d
 buildlet: http://gnot reverse peer gnot/136.243.175.38:58736 for host type host-plan9-386-0intro
  started: 2020-03-17 01:26:33.590394436 +0000 UTC m=+288111.052548900
   status: still running

Events:
  2020-03-17T01:26:33Z checking_for_snapshot 
  2020-03-17T01:26:33Z finish_checking_for_snapshot after 117.8ms
  2020-03-17T01:26:33Z get_buildlet 
  2020-03-17T01:40:42Z finish_get_buildlet after 14m8.8s
  2020-03-17T01:40:42Z using_buildlet gnot
  2020-03-17T01:40:42Z write_version_tar 
  2020-03-17T01:40:42Z get_source go@7ec4adbc919df7dbd549ccc71a2e17d8a0bafe4d
  2020-03-17T01:40:43Z finish_get_source after 0s; go@7ec4adbc919df7dbd549ccc71a2e17d8a0bafe4d
  2020-03-17T01:40:43Z write_go_src_tar 
  2020-03-17T01:40:50Z finish_write_go_src_tar after 7.54s
  2020-03-17T01:40:50Z make_and_test 
  2020-03-17T01:40:50Z make src/make.rc
 +134097.9s (now)

Build log:
plan9-386-0intro at 7ec4adbc919df7dbd549ccc71a2e17d8a0bafe4d

:: Running /tmp/workdir-gnot/go/src/make.rc with args ["/tmp/workdir-gnot/go/src/make.rc"] and env ["home=/usr/glenda" "path=.\x00/bin" "*=" "type=host-plan9-386-0intro" "rcname=gobuildlet" "pid=19030" "fn#term%=fn term% {$*}\n" "fn#newworkdir=fn newworkdir {if(test -d $workdir){for(i in `{du -a $workdir|awk '{print $2}'})chmod u+w $i;rm -rf $workdir};mkdir $workdir}\n" "status=" "fn#cd=fn cd {builtin cd $* && awd}\n" "GOROOT_BOOTSTRAP=/tmp/workdir-gnot/go1.4" "workdir=/tmp/workdir-gnot" "objtype=386" "fn#sigexit=" "cflag=" "0=/bin/gobuildlet" "WORKDIR=/tmp/workdir-gnot" "GO_BUILDER_NAME=plan9-386-0intro" "GOBIN=" "GOROOT_BOOTSTRAP=/usr/go-plan9-386-bootstrap"] in dir /tmp/workdir-gnot/go/src

Building Go cmd/dist using /usr/go-plan9-386-bootstrap
Building Go toolchain1 using /usr/go-plan9-386-bootstrap.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.

Which is not very far. This seems unexpected.

/cc @0intro Are you able to look into this?

@0intro

This comment has been minimized.

Copy link
Member

@0intro 0intro commented Mar 18, 2020

I've just restarted the builder.

@andybons

This comment has been minimized.

Copy link
Member

@andybons andybons commented Mar 23, 2020

Builder appears unstuck. Thanks, @0intro!

@andybons andybons closed this Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.