Homu times out when using try branches #903
Comments
|
The "normal" r+ workflow is that homu waits for a github status for each CI system. I’m not sure how trychoosers work. Manish said they’re only separate branches as far as homu is concerned, but What might be a solution is to add those trychooser branches to: https://github.com/servo/servo/blob/40e5a38f3c6ade2e9c1c450d0082c7064c86dfac/.taskcluster.yml#L8 … and schedule corresponding jobs (possibly none) here: |
Merged
bors-servo
pushed a commit
that referenced
this issue
Oct 16, 2018
Update homu revision This fixes #903. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/905) <!-- Reviewable:end -->
SimonSapin
added a commit
to servo/servo
that referenced
this issue
Dec 11, 2018
This is an alternative fix for servo/saltfs#903, and anticipates adding trychooser support to Taskcluster
SimonSapin
added a commit
to servo/servo
that referenced
this issue
Dec 11, 2018
This is an alternative fix for servo/saltfs#903, and anticipates adding trychooser support to Taskcluster
SimonSapin
added a commit
to servo/servo
that referenced
this issue
Dec 11, 2018
This is an alternative fix for servo/saltfs#903, and anticipates adding trychooser support to Taskcluster
SimonSapin
added a commit
to servo/homu
that referenced
this issue
Dec 11, 2018
This reverts commit 755c02c. The reverted commit was a fix for servo/saltfs#903, but that issue is also fixed by servo/servo#22426: if `.taskcluster.yml` is configured with at least one task, then taskcluster-github will set the status that Homu is waiting for.
bors-servo
pushed a commit
to servo/homu
that referenced
this issue
Dec 12, 2018
Revert "Quick fix for homu timeout on try (fixes #903)" This reverts commit 755c02c. The reverted commit was a fix for servo/saltfs#903, but that issue is also fixed by servo/servo#22426: if `.taskcluster.yml` is configured with at least one task, then taskcluster-github will set the status that Homu is waiting for. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/homu/184) <!-- Reviewable:end -->
bors-servo
pushed a commit
to servo/servo
that referenced
this issue
Dec 12, 2018
Taskcluster: start a decision task for all try-* branches This is an alternative fix for servo/saltfs#903, and anticipates adding trychooser support to Taskcluster. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/22426) <!-- Reviewable:end -->
bors-servo
pushed a commit
to servo/servo
that referenced
this issue
Dec 12, 2018
Taskcluster: start a decision task for all try-* branches This is an alternative fix for servo/saltfs#903, and anticipates adding trychooser support to Taskcluster. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/22426) <!-- Reviewable:end -->
yshui
pushed a commit
to hadeaninc/homu
that referenced
this issue
Apr 1, 2019
This reverts commit 755c02c. The reverted commit was a fix for servo/saltfs#903, but that issue is also fixed by servo/servo#22426: if `.taskcluster.yml` is configured with at least one task, then taskcluster-github will set the status that Homu is waiting for.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this started when taskcluster was introduced. Every
@bors-servo try=foonow times out after 10-11 hours instead of reporting results, even when the results are complete much sooner than that. My suspicion is that it's waiting for taskcluster results that will never come.cc @SimonSapin @Manishearth
The text was updated successfully, but these errors were encountered: