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

**URL:** <https://forum.ansible.com/t/shippable-failed-due-to-non-replicated-code-how-can-i-force-re-check/30793>\
**Category:** Ansible Developer\
**Created:** [July 16, 2019, 5:42pm UTC](https://forum.ansible.com/t/shippable-failed-due-to-non-replicated-code-how-can-i-force-re-check/30793 "2019-07-16T17:42:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![d-little](https://avatars.discourse-cdn.com/v4/letter/d/43a26b/32.png) [@d-little](https://forum.ansible.com/u/d-little)\
**Post date:** [July 16, 2019, 5:42pm UTC](https://forum.ansible.com/t/shippable-failed-due-to-non-replicated-code-how-can-i-force-re-check/30793/1 "2019-07-16T17:42:56Z")

</div>

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](https://github.com/ansible/ansible/pull/59112)  
**Shippable #132310** - [https://app.shippable.com/github/ansible/ansible/runs/132310](https://app.shippable.com/github/ansible/ansible/runs/132310)

Thanks!

---

<div class="post-metadata">

**Author:** ![d-little](https://avatars.discourse-cdn.com/v4/letter/d/43a26b/32.png) [@d-little](https://forum.ansible.com/u/d-little)\
**Post date:** [July 16, 2019, 6:01pm UTC](https://forum.ansible.com/t/shippable-failed-due-to-non-replicated-code-how-can-i-force-re-check/30793/2 "2019-07-16T18:01:28Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Kai\_Stian\_Olstad](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@Kai\_Stian\_Olstad](https://forum.ansible.com/u/Kai_Stian_Olstad)\
**Post date:** [July 16, 2019, 6:08pm UTC](https://forum.ansible.com/t/shippable-failed-due-to-non-replicated-code-how-can-i-force-re-check/30793/3 "2019-07-16T18:08:26Z")

</div>

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