Skip to content

Restore ASIM warning baseline paths - #171

Merged
mavam merged 1 commit into
mainfrom
fix-assert-baseline
Aug 6, 2026
Merged

Restore ASIM warning baseline paths#171
mavam merged 1 commit into
mainfrom
fix-assert-baseline

Conversation

@mavam

@mavam mavam commented Aug 6, 2026

Copy link
Copy Markdown
Member

🔍 Problem

  • The ASIM assertion baseline was regenerated from the Microsoft package root in Simplify null propagation in package UDOs #170.
  • CI runs the library suite from the repository root, so the diagnostic paths retain the microsoft/ prefix and fail comparison.

🛠️ Solution

Restore the repository-root path prefixes in the assertion baseline while preserving the updated diagnostic formatting.

💬 Review

The baseline-only change matches the CI invocation fixed in #168. Both release and prerelease suites pass locally (231 passed, 1 skipped).

📎 Related: #168, #170

Keep diagnostic paths aligned with the repository-root test invocation used by CI.

Assisted-by: GPT-5.6 Sol (pi 0.84.0)
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@mavam
mavam merged commit e984b9e into main Aug 6, 2026
3 checks passed
@mavam
mavam deleted the fix-assert-baseline branch August 6, 2026 14:42
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