On 3/7/25 5:30 PM, Alin Serdean wrote:
> Acked-by: Alin Gabriel Serdean <aserd...@ovn.org>
> 
> On Fri, Mar 7, 2025 at 5:23 PM Ilya Maximets <i.maxim...@ovn.org> wrote:
> 
>> We had a few issues lately with GitHub Actions being unable to checkout
>> sparse from the git.kernel.org:
>>
>>   git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
>>   Cloning into 'sparse'...
>>   fatal: unable to connect to git.kernel.org:
>>   git.kernel.org[0: 172.105.4.254]: errno=Connection timed out
>>   git.kernel.org[1: 2600:3c04::f03c:95ff:fe5e:7468]: errno=Network is
>> unreachable
>>
>> Let's try and use the official mirror of the project hosted on GitHub
>> itself.  This mirror is maintained by the main maintainer of the
>> project and mentioned in the documentation as one of the ways of
>> getting sparse:
>>   https://sparse.docs.kernel.org/en/latest/#getting-sparse
>>
>> It may also be better to not create extra load on kernel.org servers,
>> they should not be used for CI purposes.
>>
>> Signed-off-by: Ilya Maximets <i.maxim...@ovn.org>
>> ---

Thanks, Ilya and Alin!  Applied to main, 25.03, 24.09 and 24.03.  I was
thinking of applying a very slightly modified version of this to 22.03 as
well, does the following look OK to you?

diff --git a/.ci/linux-prepare.sh b/.ci/linux-prepare.sh
index eeb2c0bfa3..05ad7be70e 100755
--- a/.ci/linux-prepare.sh
+++ b/.ci/linux-prepare.sh
@@ -9,7 +9,9 @@ set -ev
 # linking against it fails.
 # Disabling sqlite support because sindex build fails and we don't
 # really need this utility being installed.
-git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
+#
+# Official mirror of the git.kernel.org/pub/scm/devel/sparse/sparse.git.
+git clone https://github.com/lucvoo/sparse
 cd sparse && make -j4 HAVE_LLVM= HAVE_SQLITE= install && cd ..
 
 # Installing wheel separately because it may be needed to build some
--

Thanks,
Dumitru


_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to