shippable failed due to non-replicated code. How can I force re-check ?

[d-little]

The Shippable CI failed on one of my PR's with the following errors:

00:01 ERROR: Commit ae0ff3dc1819347652cab7589f26ca9339c7e5f9 was not found:

00:01 

00:01 fatal: bad object ae0ff3dc1819347652cab7589f26ca9339c7e5f9

00:01 

00:01 GitHub may not have fully replicated the commit across their infrastructure.

00:01 It is also possible the commit was removed by a force push between job creation and execution.

00:01 Find the latest run for the pull request and restart failed jobs as needed.

It definitely looks like the commit did not get replicated before this Shippable task ran.  Is it possible to force checks to be re-run without submitting a do-nothing commit to the branch?

PR #59112 - https://github.com/ansible/ansible/pull/59112

Shippable #132310 - https://app.shippable.com/github/ansible/ansible/runs/132310

Thanks!

[d-little]

FWIW, I added an 'empty' commit to force the CI.  I'm still wondering if there's a better way, but for future explorers that might help.

git commit --allow-empty -m "Trigger CI"

[Kai Stian Olstad]

On 16.07.2019 20:01, d-little wrote:
> FWIW, I added an 'empty' commit to force the CI. I'm still wondering if
> there's a better way, but for future explorers that might help.

If you have search the list you would have found this
https://groups.google.com/forum/#!msg/ansible-devel/z3B6Qp3GCag/YCMshG6kAwAJ


--
Kai Stian Olstad