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

Re: [PATCH 3/5] ci: make test slicing consistent across Meson/Make

From
Patrick Steinhardt <ps@pks.im>
Date
Feb 11, 2026, 06:33 UTC
Message-ID
<aYwin2chSoz1RBFw@pks.im>
In-Reply-To
<20260210225401.GA1837188@coredump.intra.peff.net>
On Tue, Feb 10, 2026 at 05:54:01PM -0500, Jeff King wrote:
Show 17 quoted lines
> On Tue, Feb 10, 2026 at 02:15:13PM -0800, Junio C Hamano wrote:
> 
> > > diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> > > index 2b175dc5c6..1b7a16e1f1 100644
> > > --- a/.github/workflows/main.yml
> > > +++ b/.github/workflows/main.yml
> > > @@ -298,7 +298,7 @@ jobs:
> > >          path: build
> > >      - name: Test
> > >        shell: pwsh
> > > -      run: ci/run-test-slice-meson.sh build ${{matrix.nr}} 10
> > > +      run: ci/run-test-slice-meson.sh build ${{matrix.nr + 1}} 10
> > >      - name: print test failures
> > >        if: failure() && env.FAILED_TEST_ARTIFACTS != ''
> > >        shell: bash
> > 
> > Have we successfully run this one?

I haven't kicked off a GitHub workflow for this patch series. Guess I should've done that. I've created https://github.com/git/git/pull/2195 now to give v2 a test run first.

Show 26 quoted lines
> > I am getting
> > 
> > Invalid workflow file: .github/workflows/main.yml#L1
> > (Line: 153, Col: 12): Unexpected symbol: '+'. Located at position 11
> > within expression: matrix.nr + 1, (Line: 301, Col: 12): Unexpected
> > symbol: '+'. Located at position 11 within expression: matrix.nr + 1
> > 
> > https://github.com/orgs/community/discussions/25386 is a 6-year old
> > discussion so things may have changed quite a lot, but at least back
> > then the claim was
> > 
> >     Github actions doesn’t support math operations in expressions
> >     inside ${{ }}. You could add up these two numbers in bash script and
> >     then use set-env command to give its value to an environment
> >     variable ...
> > 
> > though.
> 
> Right, that's why we used pwsh syntax to do it before, in d3d6493dcf
> (ci: use Meson's new `--slice` option, 2025-07-09).
> 
> That went away in 17bd1108ea (ci(windows-meson-test): handle options and
> output like other test jobs, 2025-11-18), because the "+1" was added
> into the script itself there. It looks like the patch under discussion
> removes the +1 from the script, so we'd need to go back to the pwsh
> syntax.
Indeed, will fix. Thanks!
Patrick
Previous: Jeff KingNext: Patrick Steinhardt
Message 10 of 13 in “Some assorted fixes for GitLab CI”
  1. 0/5 Some assorted fixes for GitLab CIPatrick Steinhardt, Feb 9, 2026
  2. 1/5 ci: handle failures of test-slice helperPatrick Steinhardt, Feb 9, 2026
  3. 2/5 ci: don't skip smallest test slice in GitLabPatrick Steinhardt, Feb 9, 2026
  4. Justin ToblerFeb 9, 2026
  5. 3/5 ci: make test slicing consistent across Meson/MakePatrick Steinhardt, Feb 9, 2026
  6. Justin ToblerFeb 9, 2026
  7. Patrick SteinhardtFeb 10, 2026
  8. Junio C HamanoFeb 10, 2026
  9. Jeff KingFeb 10, 2026
  10. Patrick SteinhardtFeb 11, 2026
  11. 4/5 gitlab-ci: use "run-test-slice-meson.sh"Patrick Steinhardt, Feb 9, 2026
  12. 5/5 gitlab-ci: handle failed tests on MSVC+Meson jobPatrick Steinhardt, Feb 9, 2026
  13. Justin ToblerFeb 9, 2026

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.