Skip to content

ci: collect coverage during VFS functional tests - #1020

Closed
Tyrie Vella (tyrielv) wants to merge 1 commit into
microsoft:vfs-2.56.0from
tyrielv:tyrielv/vfs-coverage-workflow
Closed

Tyrie Vella (tyrielv) wants to merge 1 commit into
microsoft:vfs-2.56.0from
tyrielv:tyrielv/vfs-coverage-workflow

Conversation

@tyrielv

Copy link
Copy Markdown

Problem and Context

VFSForGit will instrument its CI payloads in microsoft/VFSForGit#2160.
This workflow selects the latest successful master drop, but its pinned test workflow does not start a coverage collector.
Instrumented hooks can wait about five seconds for an absent collector at each startup.

Changes

  • Update the VFSForGit functional-test workflow pin to f5daeadbc2d92eb3d3c2e4f53785715edbb3de68.
  • Use the workflow's installer manifest to start collection before service installation. Manifest-free drops keep the existing test path.

Merge Order

Merge this pin update before microsoft/VFSForGit#2160.
The updated workflow supports both current uninstrumented drops and planned instrumented drops.

VFSForGit will instrument its CI payloads in
microsoft/VFSForGit#2160. This job selects the
latest successful master drop, but the current reusable-workflow pin
starts no collector. A local hook probe took about 132 ms with collection
and 5,059 ms without it.

Use the coverage-aware workflow before instrumented master drops reach
this consumer. It starts collection before service installation and
selects the compiled source from the installer manifest. Manifest-free
drops keep the existing test path.

Signed-off-by: Tyrie Vella <tyrielv@gmail.com>
Co-authored-by: GPT-6.1 Sol
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant