aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFedor Korotkov <fedor.korotkov@gmail.com>2021-01-29 14:22:54 +0000
committerEd Maste <emaste@FreeBSD.org>2021-06-07 22:50:18 +0000
commit225605ec1681d5ac08b297aa4efbc64bcb950fc2 (patch)
tree40cc5216ac8ebc0b3a662b7dbead03dc4946360e
parent03c81af24920e14bd977f34edcd3eb7fb122db19 (diff)
downloadsrc-225605ec1681d5ac08b297aa4efbc64bcb950fc2.tar.gz
src-225605ec1681d5ac08b297aa4efbc64bcb950fc2.zip
Cirrus-CI: Use the default Git history depth
Which is `50`. I saw a few errors like `Failed to force reset to SHA: object not found!` which seems is happening because the SHA is not available because there were two commits pushed almost simultaneously and the second from the top fails with this error because the SHA is not in the history. Pull Request: https://github.com/freebsd/freebsd-src/pull/454 Comments on re-commit from emaste: Originally committed as fcb4797c90f3 and reverted in 80a840b8ba03 due to the clone operation taking significantly longer. However, I have seen many failures due to the "object not found" issue recently. 7 of 37 recent runs failed because of this, and intermittent failures like this makes CI much less useful. Prefer longer-running runs to intermittent failures.
-rw-r--r--.cirrus.yml3
1 files changed, 0 insertions, 3 deletions
diff --git a/.cirrus.yml b/.cirrus.yml
index 823d8bc2e1b0..db0e4e4c0543 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -10,9 +10,6 @@ compute_engine_instance:
memory: 24G
disk: 40
-env:
- CIRRUS_CLONE_DEPTH: 1
-
task:
name: World and kernel amd64 build and boot smoke test
timeout_in: 120m