summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/fetch2/git.py
diff options
context:
space:
mode:
authorRobert Yang <liezhi.yang@windriver.com>2024-07-07 00:20:38 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2024-07-13 23:30:07 +0100
commit7bc521ed34656165fedaef1dd98cee865092291d (patch)
treedcaaa40437311debf7e4e28d1f4dc875227657ba /bitbake/lib/bb/fetch2/git.py
parente2527cf58f4f390712641a99b276b9e0aeae01c6 (diff)
downloadpoky-7bc521ed34656165fedaef1dd98cee865092291d.tar.gz
bitbake: bitbake: tests/fetch: Update GitShallowTest for clone_shallow_local()
Update the test cases since the implementation is changed: * test_shallow_multi_one_uri() The a_branch and v0.0 had the same revision, and it required fetch a_branch and remove histories of v0.0 which were conflicted, and bitbake reported: fatal: no commits selected for shallow requests Make a_branch and v0.0 have different revs to fix the problem. And now the 'rev^' is not needed, so update self.assertRevCount() as well. * test_shallow_multi_one_uri_depths() Update self.assertRevCount(), now git only fetches the required revs. * test_shallow_fetch_missing_revs() The command is: $ git fetch --shallow-exclude=v0.0 master But master and v0.0 uses the same revision, so there is no commit to fetch. * test_shallow_fetch_missing_revs_fails() Two unneeded committs are not fetched now: - rev^ - One not specified or required tag. So update self.assertRevCount() (Bitbake rev: 48eff9d9a660ad6b9bd8b53a7dcec600ef42b1d1) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/fetch2/git.py')
0 files changed, 0 insertions, 0 deletions