Message ID | pull.1578.v2.git.1693342048633.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 6ba913629f51f5fa9f78030fe47e38d5b02e3a88 |
Headers | show |
Series | [v2] ci(linux-asan-ubsan): let's save some time | expand |
"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com> writes: > ... > In fact, it is not even just `git-p4` that is the problem (even if it > flakes often enough to be problematic in the CI builds), but really the > part about Python scripts. So let's just skip any Python parts of the > tests from being run in that job. > > For good measure, also skip the Subversion tests because debugging C > code run via Perl scripts is as much fun as debugging C code run via > Python scripts. And it will reduce the time this very expensive job > takes, which is a big benefit. > > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > --- > ... > Changes since v1: > > * Made the rationale clearer (it is not Python that flakes, but > Perforce). > * Touched up the commit message. Thanks. Merged to 'next'.
On Tue, Aug 29, 2023 at 08:47:28PM +0000, Johannes Schindelin via GitGitGadget wrote: > This commit is an attempt to reduce the pain and suffering stemming from > this particular job, simply by deciding that the benefit of running the > Python/Subversion-related tests in that job is far outweighed by its > cost. FWIW, I am in favor of this patch. I've had the same thought many times but was worried I was being too dismissive of p4/svn (which I personally do not care at all about). Omitting them from the sanitizer job (but still running the basic svn/p4 tests elsewhere) seems like a good compromise. -Peff
Jeff King <peff@peff.net> writes: > On Tue, Aug 29, 2023 at 08:47:28PM +0000, Johannes Schindelin via GitGitGadget wrote: > >> This commit is an attempt to reduce the pain and suffering stemming from >> this particular job, simply by deciding that the benefit of running the >> Python/Subversion-related tests in that job is far outweighed by its >> cost. > > FWIW, I am in favor of this patch. I've had the same thought many times > but was worried I was being too dismissive of p4/svn (which I personally > do not care at all about). Omitting them from the sanitizer job (but > still running the basic svn/p4 tests elsewhere) seems like a good > compromise. Exactly my feeling. Thanks, both.
diff --git a/ci/lib.sh b/ci/lib.sh index 369d462f130..6fbb5bade12 100755 --- a/ci/lib.sh +++ b/ci/lib.sh @@ -280,6 +280,8 @@ linux-leaks) ;; linux-asan-ubsan) export SANITIZE=address,undefined + export NO_SVN_TESTS=LetsSaveSomeTime + MAKEFLAGS="$MAKEFLAGS NO_PYTHON=YepBecauseP4FlakesTooOften" ;; esac