Skip to content

[#488] 🐛 - Dogfooding make Windows verification fixture startup and failure evidence explicit - #489

Merged
efraespada merged 5 commits into
developfrom
bugfix/488-dogfooding-make-windows-verification-fixture-startup-and-failure-evidence-explicit
Oct 13, 2026
Merged

efraespada merged 5 commits into
developfrom
bugfix/488-dogfooding-make-windows-verification-fixture-startup-and-failure-evidence-explicit

Conversation

@efraespada

@efraespada efraespada commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Two hosted Windows fixtures could hide useful acceptance evidence: the verification shell returned only exit 2, and the literal-argv fixture could fail with EPERM while removing its temporary directory after successful execution. The shell now imports trusted system modules explicitly and reports bounded child diagnostics; cleanup uses the existing finite retry pattern.

The real shell, hashing, process and argv checks remain, as do all execution deadlines and platform/coverage gates. Cleanup still fails if retries are exhausted. The change adds no production runtime or permission behavior.

Validation: normal repository hooks passed, and the final Action-managed head passed CI, native review and full hosted Mac, Ubuntu and Windows coverage/acceptance. Parent and dependency integration both used the Action and completed all six configured verification checks. Two existing cases were strengthened; no new test case is counted.

Closes #488

@docs-page

docs-page Bot commented Oct 13, 2026

Copy link
Copy Markdown

To preview the documentation for this pull request, visit the following URL:

docs.page/vypdev/copilot~489

Documentation is deployed and generated using docs.page

@vypbot vypbot changed the title test: stabilize Windows fixture startup and cleanup evidence [#488] 🐛 - Dogfooding make Windows verification fixture startup and failure evidence explicit Oct 13, 2026
@vypbot
vypbot self-requested a review October 13, 2026 14:22
@vypbot vypbot moved this to In Progress in vypdev Oct 13, 2026
@vypbot vypbot added this to vypdev Oct 13, 2026
@vypbot
vypbot changed the base branch from develop to master October 13, 2026 14:22
@vypbot
vypbot changed the base branch from master to develop October 13, 2026 14:23
@vypbot vypbot added size: M Medium-sized task with moderate complexity and effort. 75% Progress: 75% labels Oct 13, 2026
@vypbot

vypbot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Bugbot: review complete

Current status: No active findings on 8db8b7e.

Pull request · Verified commit · Workflow run

@codecov-commenter

codecov-commenter commented Oct 13, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 93.11%. Comparing base (6960aff) to head (8db8b7e).

Files with missing lines Patch % Lines
...ata/repository/project/project_board_item_query.ts 92.30% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #489      +/-   ##
===========================================
+ Coverage    93.10%   93.11%   +0.01%     
===========================================
  Files          872      872              
  Lines        27101    27119      +18     
  Branches      7846     7853       +7     
===========================================
+ Hits         25233    25253      +20     
+ Misses         746      743       -3     
- Partials      1122     1123       +1     
Files with missing lines Coverage Δ
...a/repository/project/project_board_field_update.ts 100.00% <100.00%> (ø)
...ata/repository/project/project_board_item_query.ts 97.56% <92.30%> (-2.44%) ⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vypbot

vypbot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Copilot approval · Human review needed

Status: This pull request is outside the configured approval scope.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 8db8b7e9814e; base: 6960aff8968f; reason: scope.

@efraespada

Copy link
Copy Markdown
Member Author

/copilot sync-branch --from bugfix/486-dogfooding-recover-bounded-project-item-visibility-after-linking-a-pr

…fter-linking-a-pr into bugfix/488-dogfooding-make-windows-verification-fixture-startup-and-failure-evidence-explicit
@vypbot

vypbot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Branch synchronized

bugfix/486-dogfooding-recover-bounded-project-item-visibility-after-linking-a-pr was merged into bugfix/488-dogfooding-make-windows-verification-fixture-startup-and-failure-evidence-explicit and pushed as 8db8b7e9814e472675cb8a686f21b05cf054e7fd.

6 verification checks passed.

@efraespada efraespada closed this Oct 13, 2026
@efraespada efraespada reopened this Oct 13, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in vypdev Oct 13, 2026
@efraespada
efraespada merged commit ab3d096 into develop Oct 13, 2026
16 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

75% Progress: 75% size: M Medium-sized task with moderate complexity and effort. state:verified

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

🐛🧑‍💻 - Dogfooding make Windows verification fixture startup and failure evidence explicit

3 participants