re-posting to oe-core list. While this is a bitbake question, I didn't
get any answer.. so I would like to get more attention from bitbake
-- Forwarded message --
From: Nicolas Dechesne
Date: Wed, Feb 7, 2018 at 4:04 PM
Subject: git fetcher and github pull requests
To: bitbake-devel , Ryan Harkin
we've been debugging an issue these days on our builder which ended up
do_fetch failing with
LANG=C git -c core.fsyncobjectfiles=0 fetch -f --prune --progress
git://github.com/OP-TEE/optee_test.git refs/*:refs/* failed with exit
code 128, output:
error: Could not read 48e440f5f8d033e1ace6e41f424ecf6e6d96e5f2
error: Could not read 019a8db54beb29388e1108831d2e2dc135c1cd73
It happens that these refs correspond to pull requests done on github
which existed at some point, but have been updated with newer commits,
and won't exist anymore.
the bitbake fetcher seems to be greedy and fetches refs/* which ends
up fetching pull request when fetching from github, e.g. in my
It looks inefficient to fetch and store on each builder pull requests.
I understand this is just because how PR are implemented in github,
but github is quite central, so many we should/could do something
Beyond the inefficiencies, we now are seeing unrelated build issues as well.
What do you think? Should we try to avoid fetching refs/pull/* from
github? or is it our git fetch command that needs to be improve to
work in this situation?
Openembedded-core mailing list