diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2025-02-25 11:05:25 +0000 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2025-02-26 07:45:57 +0100 |
| commit | d5d028eee38d4107821c0d2cfdb0dd04b9ba5ca3 (patch) | |
| tree | 591e2ccdf812e4ce0eda152969dbdcc177c37712 /tests | |
| parent | fe95724da2180681b7d78e9c2b9fd8438023f9ce (diff) | |
| download | qemu-d5d028eee38d4107821c0d2cfdb0dd04b9ba5ca3.zip qemu-d5d028eee38d4107821c0d2cfdb0dd04b9ba5ca3.tar.gz qemu-d5d028eee38d4107821c0d2cfdb0dd04b9ba5ca3.tar.bz2 | |
gitlab: use --refetch in check-patch/check-dco jobs
When gitlab initializes the repo checkout for a CI job, it will have
done a shallow clone with only partial history. Periodically the objects
that are omitted cause trouble with the check-patch/check-dco jobs. This
is exhibited as reporting strange errors being unable to fetch certain
objects that are known to exist.
Passing the --refetch flag to 'git fetch' causes it to not assume the
local checkout has all common objects and thus re-fetch everything that
is needed. This appears to solve the check-patch/check-dco job failures.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Message-ID: <20250225110525.2209854-1-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions