Hi Harald, On 8/13/22 02:53, Vadim Yanitskiy wrote:
Oh, wait. I am complicating things for no reason. Of course we can still clone/pull from git.osmocom.org via https://, so I can simply do s#git://git.osmocom#https://git.osmocom#. I'll submit patches soon.
I found your https://gerrit.osmocom.org/c/osmo-ci/+/28349 and fixed problems found during code review. Oliver gave CR+2, so I merged it. Now osmo-ci.git is using https:// instead of git://, so libosmo-gprs.git is now accessible by Jenkins jobs. But we're not doing good yet. == cgit is out of sync Today I noticed that cgit mirror of libosmo-gprs.git is out of sync with Gerrit/Gitea: $ git ls-remote https://git.osmocom.org/libosmo-gprs HEAD 11cbba9d9dd3423959adc6cd9200fe1ce9afd227 HEAD $ git ls-remote https://gerrit.osmocom.org/libosmo-gprs HEAD 147c95f09f5c222d8e1384d131781d8ae4cbd3d8 HEAD git ls-remote https://gitea.osmocom.org/osmocom/libosmo-gprs HEAD 147c95f09f5c222d8e1384d131781d8ae4cbd3d8 HEAD The sync worked until recently: I merged several changes via Gerrit, and they do appear at https://cgit.osmocom.org/libosmo-gprs/log/. Is there anything I could do to troubleshoot this? == Sporadic git-clone failures on Jenkins Another problem is that after the git-to-https migration, I started to observe sporadic git-clone failures in master Jenkins jobs like: + git clone https://git.osmocom.org/libosmo-abis libosmo-abis Cloning into 'libosmo-abis'... error: (curl_result = 56, http_code = 200, sha1 = 6498826eae07a02be1afc8e4f161bd1caa626e7d) error: Unable to find 6498826eae07a02be1afc8e4f161bd1caa626e7d under https://git.osmocom.org/libosmo-abis Cannot obtain needed tree 6498826eae07a02be1afc8e4f161bd1caa626e7d while processing commit e58d33153dd2bed3629b9a09fd6add58f296bd6a. error: fetch failed. + git clone https://git.osmocom.org/libosmo-sccp libosmo-sccp Cloning into 'libosmo-sccp'... error: HTTP/2 stream 0 was closed cleanly, but before getting all response header fields, treated as error (curl_result = 92, http_code = 0, sha1 = 80f1e4bfb9c161c76f04443bd03b8a2c3ce7dbd5) error: HTTP/2 stream 0 was closed cleanly, but before getting all response header fields, treated as error (curl_result = 92, http_code = 0, sha1 = 7be9bdd1632efe63b9af2d42dd355eda7883747c) error: Unable to find 7be9bdd1632efe63b9af2d42dd355eda7883747c under https://git.osmocom.org/libosmo-sccp Cannot obtain needed blob 7be9bdd1632efe63b9af2d42dd355eda7883747c while processing commit e7c8067df026fd294af2c95fbd2ceb16eeab7d74. error: fetch failed. Looks like our cgit instance is unreliable when accessed via https://. Best regards, Vadim. -- - Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte