Skip to content

JIT: Assertion failed '!"Inconsistent profile data"' in System.Text.Json.Tests with random GDV #112196

Description

@amanasifkhalid

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=940108&view=results
Build error leg or test failing:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "Assertion failed '!\"Inconsistent profile data\"'",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=940108
Error message validated: [Assertion failed '!"Inconsistent profile data"']
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/5/2025 5:32:14 PM UTC

Report

Build Definition Test Pull Request
940108 dotnet/runtime System.Text.Json.Tests.WorkItemExecution #112151

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1

Activity

  1. added this to the 10.0.0 milestone on Feb 5, 2025
  2. dotnet-policy-service commented on Feb 5, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
    See info in area-owners.md if you want to be subscribed.

  3. added
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 5, 2025
  4. EgorBo commented on Feb 5, 2025

    @EgorBo
    Member

    @amanasifkhalid FYI CI failures have to reported via https://helix.dot.net/BuildAnalysis/CreateKnownIssues so they can be tracked and mark failures as known in all PRs

  5. amanasifkhalid commented on Feb 5, 2025

    @amanasifkhalid
    ContributorAuthor

    @amanasifkhalid FYI CI failures have to reported via https://helix.dot.net/BuildAnalysis/CreateKnownIssues so they can be tracked and mark failures as known in all PRs

    Thanks for letting me know; I didn't know BA supported outerloop pipelines now. I'll update this issue to conform to it.

  6. EgorBo commented on Feb 5, 2025

    @EgorBo
    Member

    @amanasifkhalid FYI CI failures have to reported via https://helix.dot.net/BuildAnalysis/CreateKnownIssues so they can be tracked and mark failures as known in all PRs

    Thanks for letting me know; I didn't know BA supported outerloop pipelines now. I'll update this issue to conform to it.

    I am not sure BA specifically works (I think it doesn't require outerloop failures to be known), but all other things like "hits in 24 hours" should work if I am not mistaken, e.g. #111347

  7. added a commit that references this issue on Feb 6, 2025
    16782a4
  8. locked and limited conversation to collaborators on Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabarea-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ci-optionalBlocking optional rolling runsin-prThere is an active PR which will close this issue when it is merged

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions