Skip to content

SIGKILL System.Runtime.Serialization.Formatters.Tests #114287

Closed

Description

@vcsjones

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1005651
Build error leg or test failing: System.Runtime.Serialization.Formatters.Tests.WorkItemExecution
Pull request: #114266

Error Message

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

{
  "ErrorMessage": ["System.Runtime.Serialization.Formatters.Tests", "exit code 137"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1005651
Error message validated: [System.Runtime.Serialization.Formatters.Tests exit code 137]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/4/2025 11:04:40 PM UTC

Report

Summary

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

Activity

  1. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Apr 4, 2025
  2. jkotas commented on Apr 11, 2025

    @jkotas
    Member

    Binary formatter is under System.Runtime.

  3. removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 23, 2025
  4. added this to the Future milestone on Jul 23, 2025
  5. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Aug 11, 2025
  6. jeffschwMSFT commented on Aug 11, 2025

    @jeffschwMSFT
    Member

    removing blocking-clean-ci as this has not failed in 30 days

    4-Hour Hit Count 7-Day Hit Count 1-Month Count
    0 0 0
  7. danmoseley commented on Mar 24, 2026

    @danmoseley
    Contributor

    Note

    This analysis was generated by GitHub Copilot using the known-issue-history skill, which reconstructs failure timelines from the build-analysis bot's edit history.

    Failure History Analysis

    Metric Value
    Total failure events 205
    Failure periods 1 (continuous)
    First failure 2025-04-05
    Last failure 2025-07-09
    Days since last failure 257
    Peak 24h count 28
    Peak 1mo count 234

    Timeline

    • Apr 5-10, 2025: Heavy failures began immediately after filing, peaking at ~15/day in the 24h window and quickly climbing to 50+ in the monthly count.
    • Apr-Jun 2025: Sustained failures throughout, with the monthly count reaching 234.
    • Jun 17, 2025: 24h and 7d counts dropped to zero; monthly count started decaying.
    • Jul 9, 2025: Brief recurrence with 4 new failures in one day.
    • Aug 8, 2025: Monthly count fully decayed to 0. No failures since.

    This issue has been clean for ~8.5 months. Closing as resolved.

  8. locked and limited conversation to collaborators on Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions