ci-windows-msvc-xlings.yml

name: ci-windows-msvc-xlings

# mcpp driving the xlings-MANAGED MSVC toolset (`msvc@<toolset>`) — the whole
# chain, end to end: index → payload → unpack → resolve → build → run →
# remove.
#
# WHY THIS IS NOT IN ci-windows-e2e.yml, which also runs MSVC tests:
#
#   Different subject. Everything MSVC in the main suite (95_msvc_system,
#   99_msvc_native_build, 177, 180, 182) tests mcpp against the machine's own
#   Visual Studio. That is mcpp's code and nothing else's. This job tests
#   mcpp against the xlings ECOSYSTEM — a package index, a mirror, a payload
#   set, an unpack recipe — most of which lives in another repository and
#   moves on its own schedule.
#
#   Different failure meaning. When this job goes red it usually means the
#   index moved, not that the pull request broke something. Mixed into the
#   main suite that reads as "your change broke Windows", and the honest
#   signal (100+ fast tests, all about mcpp) gets buried under one slow test
#   about somebody else's package. Keeping them apart keeps both readable.
#
#   Different cost. ~380 MB of downloads (xim:msvc + xim:windows-sdk) and a
#   real toolchain install, against a suite whose other tests are seconds
#   each.
#
# The split is enforced by a capability, not by a file list: the tests carry
# `# requires: xlings-msvc`, granted only by MCPP_E2E_XLINGS_MSVC=1 below. So
# the main suite skips them by construction, and a new test joins this job by
# declaring the capability — there is no second list to keep in sync.
#
# Paired workflows: ci-windows.yml, ci-windows-e2e.yml.

on:
  workflow_call:

jobs:
  xlings-msvc:
    name: xlings-managed msvc toolset (windows x64, self-host)
    runs-on: windows-latest
    timeout-minutes: 45
    env:
      MCPP_HOME: C:\Users\runneradmin\.mcpp
    steps:
      - uses: actions/checkout@v4
      - uses: ./.github/actions/bootstrap-mcpp

      - uses: ./.github/actions/use-built-mcpp
        with:
          host: windows-x86_64

      - name: Name this commit's mcpp MCPP_SELF
        shell: bash
        run: |
          "$MCPP_FRESH" --version
          echo "MCPP_SELF=$MCPP_FRESH" >> "$GITHUB_ENV"

      - name: xlings-managed msvc e2e
        shell: bash
        timeout-minutes: 30
        env:
          # Grants the `xlings-msvc` capability. Without it these tests skip
          # everywhere, which is exactly what the main suite wants.
          MCPP_E2E_XLINGS_MSVC: '1'
          # Name what this job runs, so the job title and its contents cannot
          # drift apart. Widen the glob when a second test joins.
          E2E_ONLY: '239_*.sh'
          # THE DEFAULT PER-TEST CAP IS TOO CLOSE TO WHAT THIS TEST COSTS.
          # 239 fetches ~376 MB, and its measured durations on this runner are
          # 244 / 292 / 313 / 335 / 515s against run_all.sh's 600s default — a
          # download-bound test whose spread nearly reaches its own deadline,
          # so a slow mirror reports a red build for a correct one.
          #
          # Raised only here, where the job runs that one test and the step's
          # own `timeout-minutes: 30` is the real backstop — which is what
          # run_all.sh's comment says the per-test value is meant to sit under.
          E2E_TEST_TIMEOUT: '1500'
        run: |
          export MCPP="$MCPP_SELF"
          export MCPP_VENDORED_XLINGS="$XLINGS_BIN"
          export MCPP_E2E_TOOLCHAIN_MIRROR=GLOBAL
          "$MCPP_SELF" self config --mirror GLOBAL
          bash tests/e2e/run_all.sh

      # A run that matched nothing is a green tick for having done nothing,
      # and it looks exactly like a run that passed. E2E_ONLY is a glob typed
      # by hand; if it stops matching, say so here rather than in a report
      # nobody reads.
      - name: Fail if the filter selected no tests
        if: always()
        shell: bash
        run: |
          n=$(ls tests/e2e/239_*.sh 2>/dev/null | wc -l)
          test "$n" -gt 0 || { echo "FAIL: E2E_ONLY matched no tests"; exit 1; }
          echo "selected $n test(s)"