Skip to content

CI Windows job compiles the stub core; production D3D11/MF/WASAPI adapters can merge unbuilt #618

Description

@iamfatness

Problem

The Windows CI job compiles the stub native core. D3D11, Media Foundation encoding, WASAPI, real Zoom, RTMP/SRT, UVC, WGC, NDI, virtual-camera, and browser-host translation units can break and still merge. macOS already has the twin of the missing job (native-metal-macos with COREVIDEO_STUB=OFF and real adapters). Windows does not.

This is not #575. #575 is missing Actions secrets for the scheduled staging smoke. Application CI can be green while the production native configuration never compiled.

Evidence

Static review at 6f4f025687f02e14ce33fa012200afaf7396a536 (2026-09-24).

  • .github/workflows/ci.yml — native-shell-windows runs COREVIDEO_STUB=ON / test:native-media-core; WinUI publish is .NET, not the flagged native core
  • native/CMakeLists.txt — default COREVIDEO_STUB=ON; every COREVIDEO_WITH_D3D11|MF_ENCODER|WASAPI_*|UVC|WGC|VIRTUALCAM|RTMP_OUTPUT defaults OFF and requires COREVIDEO_ENABLE_DEV_ADAPTERS
  • scripts/test-native.ps1 — local production path, not the merge gate

Hardware tests that self-skip currently read as green proof.

Done when

  • A windows-latest job configures COREVIDEO_STUB=OFF plus the adapter flags the Windows beta actually ships.
  • The job fails on compile of those translation units. Missing DeckLink/AJA hardware is not a compile failure.
  • Self-skipped hardware tests print MISSING_EVIDENCE and cannot be the only green coverage for that adapter.
  • Do not block merge on a 60 fps soak on a shared runner. macOS already learned that lesson.
  • Show-engine is already in CI; do not reopen that. Companion / worker coverage can be a follow-up on this issue if still absent after the production native lane exists.

Related, not duplicate

Activity

  1. added
    bugSomething isn't working
    backlogRanked in docs/BACKLOG.md
    on Sep 24, 2026
  2. iamfatness commented on Sep 26, 2026

    @iamfatness
    OwnerAuthor

    PR #643 adds the non-stub Windows compile lane and explicit MISSING_EVIDENCE markers for skipped MF hardware validation. The repository currently has no ZOOM_SDK_URL Actions secret (confirmed via gh secret list), so CI cannot yet compile the private real Zoom adapter/engine. The job will enable those targets automatically when the private SDK source is configured. Keep #618 open until that CI path is green.

  3. added a commit that references this issue on Sep 26, 2026
  4. iamfatness commented on Sep 26, 2026

    @iamfatness
    OwnerAuthor

    Reopened after #643 merged. The non-stub Windows adapter/test compile lane is green, but the issue's real Zoom CI acceptance is still unmet: ZOOM_SDK_URL is absent, so the job reported MISSING_EVIDENCE and did not compile COREVIDEO_WITH_ZOOM or corevideo-zoom-engine. Keep this issue open until the private SDK source is configured and a CI run proves those targets.

  5. iamfatness commented on Sep 26, 2026

    @iamfatness
    OwnerAuthor

    Owner direction (2026-09-25): pause #618 while researching private Zoom SDK CI provisioning. The current working betas are acceptable for tonight's work. Keep the issue open and do not treat the MISSING_EVIDENCE CI path as complete; resume after the owner decides how to supply the SDK privately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogRanked in docs/BACKLOG.mdbugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions