Re: [PATCH v2 11/11] ci: run expensive tests on push builds to integration branches

From: Derrick Stolee <stolee@gmail.com>
Date: May 4, 2026, 18:35 UTC
Message-ID: <42f96e54-7b94-4075-91b1-1c2447b93322@gmail.com>
In-Reply-To: <1eaaa7fad7a1432dd97ffdd7c45e8162f61bc302.1777914508.git.gitgitgadget@gmail.com>

On 5/4/2026 1:08 PM, Johannes Schindelin via GitGitGadget wrote:

Show 8 quoted lines

> From: Johannes Schindelin <johannes.schindelin@gmx.de>
> 
> Derrick Stolee suggested [1] that expensive tests should be run at a
> regular cadence rather than on every PR iteration. Gate GIT_TEST_LONG
> on push builds to the integration branches (next, master, main, maint)
> so that the EXPENSIVE prereq is satisfied there but not during PR
> validation, where the extra minutes of wall-clock time do not justify
> themselves.

I like that this will be run as part of regular updates to the important branches. The important bit after that is whether or not a human pays attention to the signal of these builds.

Junio: Do you pay attention to CI breaks when you push to
'master'?

One way to help this procedure could be to have GitHub CI failures trigger new issues, which could then be more easily viewed and noticed by the community watching the repo. This is of course out-of-scope for this patch series, but could be considered in the future.

Thanks, -Stolee