From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fhigh-b6-smtp.messagingengine.com (fhigh-b6-smtp.messagingengine.com [202.12.124.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4E50C42189A for ; Mon, 29 Jun 2026 16:19:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=202.12.124.157 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782749956; cv=none; b=fmIw2VE6p2O5nVutBnEucJ+tWMeAXENvlCIjeC7rpA4R3BosEfef2e5S1XIMqqTQWwiEloAv6VTKLBA3IGrMaeb0NHGyrNZ1pLixDcehEamVon/LantpnundDjb0iOh5x+coJAhGtpjKJQLWGn1uZ8PLhK3wyEyJAHdWossXoIw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782749956; c=relaxed/simple; bh=Zj4N4Wr8UNBTXFwV43jikYKruh93rgHHw0JxIF8XG7I=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=h7Q5Sj6PWmIm7TvneeyLIDnpfNkBJD5te/ENXRamVKXgYvgYtd4Uee3GRyy08hg6NHZdF6qmgTpd+VToGYH33HU5DhkSSXNnc3jd4ot161VOjv/AQy08thwsLGC5/8nczoMvv/kEXjFUZSbrjvvMaBSnzZhSy1Uzawu1xpGv/Ck= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=pobox.com; spf=pass smtp.mailfrom=pobox.com; dkim=pass (2048-bit key) header.d=pobox.com header.i=@pobox.com header.b=gmRpz49E; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=GR98mR2g; arc=none smtp.client-ip=202.12.124.157 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=pobox.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pobox.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pobox.com header.i=@pobox.com header.b="gmRpz49E"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="GR98mR2g" Received: from phl-compute-05.internal (phl-compute-05.internal [10.202.2.45]) by mailfhigh.stl.internal (Postfix) with ESMTP id 41C1E7A00D0; Mon, 29 Jun 2026 12:19:13 -0400 (EDT) Received: from phl-frontend-02 ([10.202.2.161]) by phl-compute-05.internal (MEProxy); Mon, 29 Jun 2026 12:19:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pobox.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1782749953; x=1782836353; bh=LB2RSAXHsi E0WE1T9AmtZMXnmme8UM3P8o3IoEDHcdg=; b=gmRpz49E6ILvWlUircpbxaD4nd AXpn90kMVmGtP5XNAB2Gnaf7DvsQBqBaP3chGCI4ukBTMZUbzXU7DaIkLxafENm2 xorRCXMeF0bAOxX3rXIFtZ/kkykCpWRYiif1QNYtbPw33gBnswpMqhsm/3Nvc4j0 7X0Hfxck/is1iEMwNTHHcwWrecRMHgDjzaHpxd3NcE3DSN21k9a156TcznD6eF8o bwucsVTtwTmzxrLZx39kpHUpM/D1rOW5d/usXC8EOWX33QHjkYsOO/1HRHnlfhOZ DdiVx2RdOKkq/Zqvo4up7KzYHy280M4M7FL8SWM5gU1EKomAElHTIciR0hUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1782749953; x=1782836353; bh=LB2RSAXHsiE0WE1T9AmtZMXnmme8UM3P8o3 IoEDHcdg=; b=GR98mR2gpOe8ABqp+obdOtjZEagOjV+Nkdlz2zh8FgPMwx+m3Jw m74XWtGhIpY06o3L/b9gVYjRPncW/O36ao7SKmYHs5MBNAh99UDa4yUFr/Jm/fWE xs52SXX68Hv7kkP7HaHSzOvHzdqt6IzJuYqKvtrOu5+/6PCZ01Td3zVeA0cGZv9L iEKCleonoQDWoR9WyazrKVKLGC18IOeoT8A+wieD9LGSKYy+L/QizJ78kprRvpyc 8n0lENOiGDm15YWfL4oUXxGgZUS3Vr28LWMUtnNDaCI7nqGPOcaElfUvE+wf4Z4d WpWOdd5IgO5xKS8gZOTd7ANYmH2uhyFrPIw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTEeSda8Sd5giesJ/CSmmjlBd8Tp6vLOxKzTwYbQtI8a0itHFxa7V7in2wVZZJcHTs Dz/e4cmNaaKAyIT9lgZczbBAnE9fqlQcoNku2BqQKupINdh+SLDFhFMYerqIQspddxPEmp sC3wpTuK2Dq6Z615jSprm+wyxsTTqj3lBdpRni6l7julTSOcuAku0UkJM17ZQkc2asN/tT 3QYaKAC6fZ7m5K/TI1S0EYA1HUTpC62HKUIinHOyhKjIrA4SWNJ8D6jme85Ay8k1Boancb JOw9ElCJ1E60asTVNYsEfy8kmJVNL/CrZWocmDFz5MJKfpqUZGQnGq/LPi4vYTHFwLjXZD GrMn/ysnAmF+TbFpi9X4L7+i/45hMPeoNK9X3wmzGuqdQD+I4s4UjPCAqsA+5wuzmwhy9V OkAPKs9mYmG+zha2n5CXfX1hSYMO75NTiygpi/qyzcL+rViL9kCfgMi28YTygZFfAY8mI5 El0y4wSGDbRMDIA6uuDZoZNPc7vhrdgCW7xnLKeG+07P0zdtHvtOkQGl2vVYafLnzTae+0 LspTj+9il9DfASwUN3lgJ5YqeLlixEquMWWHdjBLVu0OvCpxbv6+jipofQhL4GATXxLtoA 7HojxS6ZAUPeGbhg6oV/saHyr9tX9aSBKJsiIyJEb6rfLoe+lVEaN8ANBBKA X-ME-Proxy: Feedback-ID: if26b431b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 29 Jun 2026 12:19:12 -0400 (EDT) From: Junio C Hamano To: Patrick Steinhardt Cc: Jeff King , Michael Montalbo , git@vger.kernel.org Subject: Re: [PATCH 0/3] fixing expensive http test timeouts In-Reply-To: (Patrick Steinhardt's message of "Mon, 29 Jun 2026 18:09:35 +0200") References: <20260626051657.GB3138423@coredump.intra.peff.net> <20260628075716.GA3525066@coredump.intra.peff.net> Date: Mon, 29 Jun 2026 09:19:11 -0700 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Patrick Steinhardt writes: >> pushes only to "cast in stone" branches. If there are other >> branches that deserve to be tested with TEST_LONG upon other events >> that the existing GitHub Actions CI does not trigger, it may be good >> to have GitLab CI cover them, perhaps? > > I'm a bit hesitant to do such a split, mostly because the canonical > source of truth that the project typically uses is GitHub's CI. So I > want us at GitLab to be able to catch the same issues that GitHub would > flag. And if GitLab's CI stopped detecting everything that GitHub does, > then the result would likely be that we often create merge requests on > both platforms, which would only result in more wasted resources. I didn't suggest splitting them into two circles that overlap but each with area only it covers, though. GitLab's coverage can be superset to GitHub's and that would satify what I suggested. FWIW, I do not consider GitHub's CI "the canonical source" at all. It is a very handy service to use to check how well we are doing, but from time to time it has its own hiccups ;-). What can we do to make the visibility of GitLab's CI more prominent? I know where the CI jobs that are triggered when I push out the integration branches are found at GitHub's website[*], but I do not think I know the corresponding one at GitLab, for example, and I think that is a shame. [Footnote] *1* I just made https://tinyurl.com/github-gitci that points at https://github.com/git/git/actions/workflows/main.yml?query=event%3Apush+actor%3Agitster