[CI Postmortem] Flaky: BitmapContextTest.CreateAdaptive_2 on iOS

[rolfbjarne]

Flaky Test Report (automated)

Test: MonoTouchFixtures.CoreGraphics.BitmapContextTest.CreateAdaptive_2
Platform: iOS
Period: May 4–11, 2026

Occurrence Summary

PR	Build	Bot	Direct Link
#25375	14048285	VSCXSDKs-MINI-024	Run tests
#23602	14047016	VSCXSDKs-MINI-026	Run tests
#25303	14036728	VSCXSDKs-MINI-038	Run tests

Total: 3 builds across 3 PRs

Error Details

  calledOnReleaseInfo#2
  Expected: False
  But was:  True

The test asserts that calledOnReleaseInfo is not called after certain CoreGraphics bitmap context operations. The release callback is being invoked unexpectedly — likely a race condition or GC timing issue.

---

This issue was automatically generated by CI post-mortem analysis.

[rolfbjarne]

This might be a duplicate of #25171.

[rolfbjarne]

CI Post-Mortem Update (May 25 – Jun 1, 2026)

A variant of this flaky test appeared this week — CreateAdaptive_3 on tvOS (the existing issue tracks CreateAdaptive_2 on iOS):

PR	Build	Platform	Config	Error
#25538	14204981	tvOS	Release (compat inline Class.GetHandle)	calledOnReleaseInfo#3 Expected: False But was: True
#25539	14205048	tvOS	Release (compat inline Class.GetHandle)	Same
#25568	14242688	tvOS	Release (compat inline Class.GetHandle)	Same

Full test name: MonoTouchFixtures.CoreGraphics.BitmapContextTest.CreateAdaptive_3

This confirms the same family of race conditions exists across platforms (iOS _2, tvOS _3) and is triggered specifically in the "compat inline Class.GetHandle" configuration. The test verifies callback behavior on object release, which is inherently timing-sensitive.

---

Updated by automated CI post-mortem analysis.