On 3/10/25 1:29 PM, Ilya Maximets wrote: > On 3/10/25 13:21, Dumitru Ceara wrote: >> On 3/10/25 1:18 PM, Ilya Maximets wrote: >>> On 3/10/25 13:08, Dumitru Ceara wrote: >>>> On 3/7/25 5:30 PM, Alin Serdean wrote: >>>>> Acked-by: Alin Gabriel Serdean <[email protected]> >>>>> >>>>> On Fri, Mar 7, 2025 at 5:23 PM Ilya Maximets <[email protected]> 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 <[email protected]> >>>>>> --- >>>> >>>> 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? >>> >>> Looks OK. An alternative is to adapt the OVS change: >>> >>> https://patchwork.ozlabs.org/project/openvswitch/patch/[email protected]/ >>> >> >> Thanks, I decided to use the diff below in the end as we don't expect >> too many changes to 22.03 and it felt closer to what we have on the >> other (maintained) stable branches. > > Sure. Could you also apply to all the intermediate branches? > Commits that go to 22.03 should normally be applied to all other > branches as well, even if no releases are cut from them. And CI > on those branches will be triggered when backporting critical or > security fixes to LTS. >
Done, thanks for reminding me about that. >> >>>> >>>> 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 >>>> >> >> Regards, >> Dumitru >> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
