CI timeout in System.Data.Tests.DataSetTest2.Bug537229_BinFormatSerializer_Test

[amanasifkhalid]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=704655
Build error leg or test failing: System.Data.Common.Tests.WorkItemExecution
Pull request: #103319

Error Message

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

{
  "ErrorMessage": [
    "[Long Running Test] 'System.Data.Tests.DataSetTest2.Bug537229_BinFormatSerializer_Test'",
    "Command timed out, and was killed"
  ],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=704655
Error message validated: [[Long Running Test] 'System.Data.Tests.DataSetTest2.Bug537229_BinFormatSerializer_Test' Command timed out, and was killed]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/12/2024 4:02:55 PM UTC

Report

Summary

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

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

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

[SamMonoRT]

@eiriktsarpalis - is this something you can take a quick look at?

[eiriktsarpalis]

Seems to be an old test using BinaryFormatter. Perhaps related to BF being phased out?

cc @bartonjs @adamsitnik

[bartonjs]

It seems to be using BinaryFormatter directly, not via System.Resources.Extensions, so Adam's changes wouldn't be affecting it. And mine haven't gone in yet. So, unless the test is psychic and knows BinaryFormatter will be turned off in the next day or two, it seems coincidental.

That said, when I merge in (today or tomorrow) this test will be disabled. No tests will be able to use BinaryFormatter until we get a package published, just because of how our build system works and how we chose to solve the BF-legacy problem, so it will at least stop showing up as an intermittent CI failure.

[SamMonoRT]

Assigning to @bartonjs for tracking.

[jeffschwMSFT]

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

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

[SamMonoRT]

@bartonjs - this is still marked for 9.0.0 -- please take a look and adjust milestone if necessary, or can we close the issue?