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

Bug report: long delay between `bors try` succeeding and the `try - Build succeeded` comment being posted #739

Open
DilumAluthge opened this issue Sep 9, 2019 · 0 comments

Comments

@DilumAluthge
Copy link
Contributor

commented Sep 9, 2019

Cross-posted from this forum post.

When I comment bors r+, as soon as all of the required status checks have succeeded, Bors comments Build succeeded and merges the pull request(s). This happens almost immediately (that is, within one or two minutes of all of the required status checks finishing).

In contrast, when I comment bors try, there is often a long delay between all of the required status checks succeeding and Bors commenting try - Build succeeded. In many cases, there is a delay of 30 minutes or greater between all of the required status checks succeeding and Bors posting the try - Build succeeded comment.

Am I doing something wrong? Or is this a bug in Bors?

See below for an example.


This example is for the pull request: bcbi/BorsTestRepository.jl#7

I first post a comment with the contents bors try.

Four minutes after I posted the bors try comment, the only required status check has passed, but there is no comment from Bors.
try-1

Seven minutes after posting bors try, still no comment.
try-2

Ten minutes:
try-3

Thirty-one minutes:
try-4

Thirty-four minutes after I posted the bors try comment, Bors finally posts the try - Build succeeded comment.
try-finished

In contrast, when I comment bors r+, Bors comments Build succeeded and merges the pull request less than two minutes after I commented bors r+.
r-plus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.