git/list[1] front-page[2] threads[3] people[4] search[5] about
 

yz/p4-py3, was Re: What's cooking in git.git (Jan 2020, #04; Wed, 22)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 23, 2020, 12:11 UTC
Message-ID
<nycvar.QRO.7.76.6.2001231306351.46@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqftg6671g.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, 22 Jan 2020, Junio C Hamano wrote:
Show 26 quoted lines
> SZEDER Gábor <szeder.dev@gmail.com> writes:
>
> > On Wed, Jan 22, 2020 at 02:18:05PM -0800, Junio C Hamano wrote:
> >> * yz/p4-py3 (2020-01-15) 14 commits
> >>  - ci: also run linux-gcc pipeline with python3.5 environment
> >
> > I still think that this last patch needs to be reworked before this
> > series is merged any further.
> >
> > The only Python script we have is 'git p4', so the Python version is
> > only relevant for 'git p4' tests ('t98*'), while the rest of Git and
> > the test suite couldn't care less [1].  This patch, however, not only
> > builds Git and runs the full test suite for each of the two Python
> > versions, but, worse, runs the full test suite _twice_ for each, first
> > as a "regular" test run and then again with all the GIT_TEST_* knobs
> > enabled.  Consequently, it adds ~50mins to every build's runtime.
> >
> > That's just too wasteful.
>
> Thanks for a reminder.  Yes, I do recall you raised the above point
> and I agree with the assessment.
>
> What's the ideal endgame wrt the tests?  Build with Py$N and run
> full test suite once, and run full test suite again with the unusual
> knobs enabled, which is what is done without this series, plus build
> with Py(5-$N) and run and run only t98?? tests?

Should we declare `t98xx` to be the namespace for the Python-based scripts, or alternatively declare that we won't ever include another Python script but `git-p4`?

But yes, I think that we should probably "tack on" the Python 3.x tests to the `linux-gcc` job.

Or maybe finally split this job into three: one job that does what `linux-gcc` suggests, a `linux-gcc-knobs` one that sets all those `GIT_*` variables, and a python3x one that only runs t98*.sh.

The reason to split it off is this: on rare occasion, I have to restart the `linux-gcc` job because _one_ of those `git-p4` tests failed due to some reason or other, probably timing-related, I did not have time to investigate this. Having to re-run the entire test suite, twice, just to work around those flaky tests is rather wasteful.

That would actually be my prereference. If people agree, I will revive https://github.com/gitgitgadget/git/pull/266.

Ciao, Dscho

Previous: Junio C HamanoNext: Yang Zhao
Message 6 of 33 in “What's cooking in git.git (Jan 2020, #04; Wed, 22)”
  1. Junio C HamanoJan 22, 2020
  2. Elijah NewrenJan 22, 2020
  3. Junio C HamanoJan 22, 2020
  4. SZEDER GáborJan 22, 2020
  5. Junio C HamanoJan 23, 2020
  6. yz/p4-py3, was Re: What's cooking in git.git (Jan 2020, #04; Wed, 22)Johannes Schindelin, Jan 23, 2020
  7. Yang ZhaoJan 23, 2020
  8. SZEDER GáborJan 27, 2020
  9. SZEDER GáborJan 23, 2020
  10. SZEDER GáborJan 23, 2020
  11. Junio C HamanoJan 23, 2020
  12. Yang ZhaoJan 24, 2020
  13. Johannes SchindelinJan 25, 2020
  14. SZEDER GáborJan 25, 2020
  15. Johannes SchindelinJan 26, 2020
  16. Johannes SchindelinJan 23, 2020
  17. SZEDER GáborJan 24, 2020
  18. Johannes SchindelinJan 25, 2020
  19. Junio C HamanoFeb 5, 2020
  20. SZEDER GáborFeb 6, 2020
  21. Johannes SchindelinFeb 6, 2020
  22. SZEDER GáborFeb 6, 2020
  23. Johannes SchindelinFeb 6, 2020
  24. Johannes SchindelinJan 23, 2020
  25. Denton LiuJan 23, 2020
  26. Junio C HamanoJan 23, 2020
  27. Christian CouderJan 23, 2020
  28. Junio C HamanoJan 23, 2020
  29. Denton LiuJan 26, 2020
  30. Junio C HamanoJan 27, 2020
  31. .mailmap: fix erroneous authorship for Derrick StoleeDenton Liu, Jan 27, 2020
  32. Junio C HamanoJan 28, 2020
  33. Denton LiuJan 29, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.