microsoft / microsoft/CLRInstrumentationEngine

EmittedDynamicCodeTest fails locally

Open
#312 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
102
Forks
52
Avg merge
13h 11m
Merged PRs (30d)
6

Description

Could just be an outdated baseline. This is the error:

Assert.Fail failed. Baseline value does not equal output value
IL_0000 nopIL_0001 nopIL_0002 ldstr 0x70000324IL_0007 call 0xa00001fIL_000c nopIL_000d ret
IL_0000 nopIL_0001 nopIL_0002 ldstr 0x7000030eIL_0007 call 0xa00001fIL_000c nopIL_000d ret

Looks like a mismatch in the string token

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running EmittedDynamicCodeTest and capture the emitted output alongside the stored baseline. Compare the string-token differences shown in the report and determine whether the baseline or generated output is incorrect. Done means the test has a justified, reproducible result and passes with the correct baseline.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.