[CI Failure] Flaky: ParentProcessLifetimeScopesExecutableAndContainerToParentProcess fails due to DCP timestamp parsing BadRequest #18755

Activity

1. github-actions

   added

   test-failure

   ci-failure-cause

   on Jul 13, 2026
2. radical commented on Aug 29, 2026

   

   Ankit Jain (radical)

   on Aug 29, 2026

   Member

   More actions

   [automated] The CI shepherd is watching this failure.

   Current assessment: Watch this single-test-occurrence for another independent failure of the same test on a different day.

   Evidence reviewed:

   • issue:18755
   • run:29217376246
   • pr:18752

   Evidence still needed:

   • verified-fix-or-current-recurrence-check

   Reassess when: After another independent failure of the same test on a different day or positive recovery.

   No quarantine, retry, closure, or investigation has been started.
3. davidfowl commented on Oct 31, 2026

   

   David Fowler (davidfowl)

   on Oct 31, 2026 – with Copilot SWE Agent

   Collaborator

   More actions

   This failure's root cause was fixed by #18798 (merged 2026-07-16).

   Root cause: On Linux, the parent-process identity timestamp is boot-relative, stored as an offset from DateTime.MinValue. When the value fell on a whole second, System.Text.Json's default DateTime converter trimmed the fractional part and wrote "0001-01-01T00:06:30Z". DCP parses monitorTimestamp as Kubernetes metav1.MicroTime, which requires exactly six fractional digits, so it returned 400 BadRequest. #18798 added KubernetesMicroTimeJsonConverter, which always writes the fixed-width form (0001-01-01T00:06:30.000000Z).

   Evidence:

   • The only recorded occurrences (2026-07-13 for [CI Failure] Flaky: ParentProcessLifetimeScopesExecutableAndContainerToParentProcess fails due to DCP timestamp parsing BadRequest #18755, 2026-07-15 for [CI Failure] Flaky: ParentProcessLifetimeReusesResourcesAcrossAppRestartsAndStopsWhenParentExits fails due to DCP timestamp parsing BadRequest #18794) come before the Fix DCP monitor timestamp serialization #18798 merge.
   • The regression tests MonitorTimestamps_SerializeToDcpMicroTimeWireContract and MonitorTimestamps_DeserializeFromDcpMicroTimeWireContract (in tests/Aspire.Hosting.Tests/Dcp/DcpExecutorTests.cs) are on main and use this exact failing input.
   • I found no later occurrences or new issues for the ParentProcessLifetime tests.

   #18798 said "Related to #18794" rather than "Fixes", so this issue wasn't closed automatically. I suggest closing it as fixed by #18798.

   🤖 Posted by AspireAgent (AI Agent)
4. davidfowl commented on Nov 1, 2026

   

   David Fowler (davidfowl)

   on Nov 1, 2026 – with Copilot SWE Agent

   Collaborator

   More actions

   Closure recommendation: no recurrence in 7 days of CI

   • Window: ci.yml attempt-1 runs from 2026-10-25T10:57Z to 2026-11-01T09:51Z (824 runs). I grepped every failed test-job log in that window (968 of 968 downloaded).
   • Test: DistributedApplicationTests.ParentProcessLifetimeScopesExecutableAndContainerToParentProcess. It's still present on main (1bccada) and requires a container runtime, so it runs on Linux.
   • Aspire.Hosting.Tests Linux shards: 63 main runs (441 shard jobs) and 198 PR runs (1,386 shard jobs).
   • Failures: 0, and the DCP timestamp-parsing BadRequest signature doesn't appear in any failed log.
   • Last recorded occurrence: 2026-07-13, run 29217376246.
   • Fixing PR: none identified.

   I recommend closing this. Reopen it if the signature comes back.

   🤖 Posted by AspireAgent (AI Agent)