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/cmd/coordinator: doesn't seem to be reporting the right elapsed time for aix-ppc64 trybot #38363

Closed
ianlancetaylor opened this issue Apr 10, 2020 · 4 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@ianlancetaylor
Copy link
Contributor

When I look at https://farmer.golang.org/try?commit=37ab01eb right now, at Fri 10 Apr 2020 06:48:51 PM UTC, I see

aix-ppc64 | (running) | aix-ppc64 rev 37ab01eb (trybot set for Id0c34c2); running; http://power8-aix-host1 reverse peer power8-aix-host1/140.211.9.26:52500 for host type host-aix-ppc64-osuosl, 2h37m19s ago ...
                      |   2020-04-10T16:39:15Z finish_write_go_src_tar after 5.48s
                      |   2020-04-10T16:39:15Z make_and_test
                      |    2020-04-10T16:39:15Z make src/make.bash
                      |  +7692.8s (now)

The timestamps are more than 50,000 seconds ago, not 7692 seconds ago.

Why do we see the wrong elapsed time?

And what is happening with the AIX builder?

Thanks.

CC @dmitshur

@ianlancetaylor ianlancetaylor added Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Apr 10, 2020
@ianlancetaylor ianlancetaylor added this to the Unreleased milestone Apr 10, 2020
@dmitshur dmitshur changed the title x/build: trybot farmer doesn't seem to be reporting the right elapsed time x/build/cmd/coordinator: doesn't seem to be reporting the right elapsed time for aix-ppc64 trybot Apr 10, 2020
@dmitshur
Copy link
Contributor

dmitshur commented Apr 10, 2020

The timestamps are more than 50,000 seconds ago

Which timestamps are you referring to? The ones I see in the snippet above are from 3~ hours ago:

t, err := time.Parse(time.RFC3339, "2020-04-10T16:39:15Z")
if err != nil { panic(err) }
fmt.Println(time.Since(t))
// Output: 3h5m32.054424s

For context, aix-ppc64 is a reverse builder (meaning it's run externally and connects to the coordinator to ask for work; it's not managed by the coordinator) and there is only one instance. The coordinator was redeployed 3.5 hours ago (farmer.golang.org displays "Uptime 3h35m55s."). It seems https://farmer.golang.org/try?commit=37ab01eb was the first trybot run that picked up the aix-ppc64 builder, but the builder is stuck on:

Building Go cmd/dist using /opt/freeware/lib/golang. (go1.13 aix/ppc64)
Building Go toolchain1 using /opt/freeware/lib/golang.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.

It might be worth canceling that trybot run (by deleting the Run-TryBot+1 vote) and letting it try again, perhaps the next time it won't get stuck. But if that doesn't help, then there must be something up with the builder.

/cc @trex58

@ianlancetaylor
Copy link
Contributor Author

I'm sorry, you're right, I did misread the timestamps. I'll close this issue.

@panjf2000
Copy link
Member

Again, it gets stuck in the same place.
https://farmer.golang.org/try?commit=efd5d44c

@panjf2000
Copy link
Member

Building Go cmd/dist using /opt/freeware/lib/golang. (go1.13 aix/ppc64)
Building Go toolchain1 using /opt/freeware/lib/golang.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.

@golang golang locked and limited conversation to collaborators Apr 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

4 participants