certain github pulls take a long time

[lance_lyons]

We have some CI builds whose github incremental updates will take a long time occasionally while other times its very fast.  I am not sure what is going on.

On the slow pulls we get this error.

simple    03-Oct-2016 10:20:53    Fetching 'refs/heads/master' from 'https://github.com/company/company.Net.git'. Will try to do a shallow fetch.
simple    03-Oct-2016 10:21:12    From https://github.com/company/company.Net
simple    03-Oct-2016 10:21:12     + 6f19893...5558192 master     -> master  (forced update)
simple    03-Oct-2016 10:21:12    Checking out revision cb0423b00ce1992ee51c966d8be3dbbbfec38f49.
simple    03-Oct-2016 10:21:12    fatal: reference is not a tree: cb0423b00ce1992ee51c966d8be3dbbbfec38f49

error    03-Oct-2016 10:21:12    Checkout to revision cb0423b00ce1992ee51c966d8be3dbbbfec38f49 has failed.

simple    03-Oct-2016 10:21:12    Warning: failed to checkout source code to directory 'E:\bamboo-agent-home\xml-data\build-dir\NET451-ONLOGIN-JOB1', trying to recover...

s

on the CI's with faster github pulls,  we dont have this error and its more like

simple    02-Oct-2016 09:35:22    Fetching 'refs/heads/master' from 'https://github.com/company/company.Net.git'. Will try to do a shallow fetch.
simple    02-Oct-2016 09:35:31    From https://github.com/company/company.Net
simple    02-Oct-2016 09:35:31     + f02af04...6f19893 master     -> master  (forced update)
simple    02-Oct-2016 09:35:31    Checking out revision 6f198932db512aa955c0d900cc7163ec1ba7192e.
simple    02-Oct-2016 09:35:47    Already on 'master'

Any ideas on why this might happen.  Its the same CI build.    Is the one that fails pulling from a repo that had a few changes while the other pull had no changes?

[Przemek Bruski]

In the first scenario, fetch recovery code path is executed.

That means that Bamboo will fetch all git refs instead of just the one you need. Is this a custom revision build? If not, please contact support, because this look like a bug.