-
Notifications
You must be signed in to change notification settings - Fork 3
[v0.17 proof] Measure Windows linker time from an explicit boundary #1635
Copy link
Copy link
Open
1 / 11 of 1 issue completedOpen
1 / 11 of 1 issue completed
Copy link
Labels
bugSomething isn't workingSomething isn't workingepic:performance-opsPerformance, scale, sidecar SLA, and artifact operationsPerformance, scale, sidecar SLA, and artifact operationsphase:next-waveActive next implementation waveActive next implementation wavepriority:p2Important follow-up for next release waveImportant follow-up for next release wavesaga:codestory-intelligenceCodeStory product-grade intelligence sagaCodeStory product-grade intelligence sagatype:harnessBenchmark or verification harness workBenchmark or verification harness work
Milestone
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingepic:performance-opsPerformance, scale, sidecar SLA, and artifact operationsPerformance, scale, sidecar SLA, and artifact operationsphase:next-waveActive next implementation waveActive next implementation wavepriority:p2Important follow-up for next release waveImportant follow-up for next release wavesaga:codestory-intelligenceCodeStory product-grade intelligence sagaCodeStory product-grade intelligence sagatype:harnessBenchmark or verification harness workBenchmark or verification harness work
Projects
StatusShow more project fields
Todo
Context
Windows package timing in the 0.16.3 release train reported linker evidence from a textual match that also accepted the Rust build line
Compiling time v0.3.47. That is the dependency namedtime, not a linker duration.The package graph, archive identity, and Windows Vulkan runtime proof all passed. The defect is telemetry-only and was explicitly accepted as a post-release follow-up.
Acceptance
Compiling time v0.3.47must not satisfy linker-timing evidence.Refs #1611
Refs #1179
v0.17 issue-map role — 2026-08-01\n\nThis issue remains the exact-candidate linker-timing evidence tracker. The workflow/harness source repair is isolated in #1709; its implementation PR closes #1709 only. Do not use #1635 itself as a stack layer.