Any reason for the lack of "retry" command?

Support
#1

servo-bors has retry, and it’s useful in a number of cases:

  • timeouts
  • sporadic CI errors, e.g. inability to download sources
  • intermittent code errors that we’d like to skip (for now!)

I’m really missing it in bors… Typying “bors r=” again (and, sometimes, again) is annoying.

#2

Any reason for the lack of retry command?

Not really. It just hasn’t been implemented yet.

#3

Do you see the need for it? Is it on the roadmap?

#4

Yeah.

Bors-NG doesn’t really have a roadmap, but yes.

#5

You'll be happy to know that bors-ng has retry now!

1 Like
#6

I don’t think it’s working correctly in all cases, e.g. this command didn’t trigger any reaction from bors: https://github.com/gfx-rs/gfx/pull/2164#issuecomment-399525678

1 Like