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?
to your account
According to the farmer page, the dragonfly builders are stacking the builds up without (probably) finishing them.
host-dragonfly-amd64-5_8: 1234 waiting (oldest 42h1m51s, newest 1m52s, progress 2m53s)
host-dragonfly-amd64-master: 1259 waiting (oldest 42h1m26s, newest 1m52s, progress 5m51s)
Not sure what's going on or how to troubleshoot. Can you please give us a hint?
The text was updated successfully, but these errors were encountered:
Looking at it now, I see both builders are in use:
dragonfly-amd64 rev 3e524ee6 (sub-repo review rev 2465c8e7); running; http://dragonflybsd-amd64 reverse peer dragonflybsd-amd64/184.108.40.206:51429 for host type host-dragonfly-amd64-master, 2h37m45s ago
2021-03-03T17:38:41Z finish_write_go_src_tar after 6.99s
2021-03-03T17:38:41Z make src/make.bash
dragonfly-amd64-5_8 rev 3e524ee6 (sub-repo website rev 02ef8fa5); running; http://dragonflybsd-amd64 reverse peer dragonflybsd-amd64/220.127.116.11:50368 for host type host-dragonfly-amd64-5_8, 2h37m37s ago
2021-03-03T17:38:19Z finish_write_go_src_tar after 5.82s
2021-03-03T17:38:19Z make src/make.bash
I think the large waiting number just means there's a lot of old commits that are available to be built. As long as it's actively working on recent commits, I don't think this is a problem.
Sorry, something went wrong.
Amazing, the backlog is not decreasing at all:
host-dragonfly-amd64-5_8: 2021 waiting (oldest 256h43m15s, newest 11m48s)
host-dragonfly-amd64-master: 2472 waiting (oldest 256h42m50s, newest 11m48s, progress 25m21s)
It has come down by this time:
host-dragonfly-amd64-5_8: 518 waiting (oldest 24h38m57s, newest 2h30m48s, progress 2s)
host-dragonfly-amd64-master: 552 waiting (oldest 24h38m57s, newest 2h30m36s, progress 2m9s)
Even though it's a large number, it is stable, and it's consistent with how coordinator has behaved for a while.
I don't think there's a problem or something to do here at this time, but we can reopen or revisit this when there's more actionable information available.
No branches or pull requests