zeroshade commented on PR #958: URL: https://github.com/apache/arrow-go/pull/958#issuecomment-5685766623
Pushed a follow-up in 797891462301: - Capture machine metadata on each benchmark runner and carry it through the combined upload, rather than attributing measurements to the combine runner. - Require explicit results/provenance arguments for reuse; ordinary local runs always take fresh measurements. - Preserve spaces during aggregation, add the portable timeout fallback, and use the current repository-pinned artifact actions. Verified with two real Go benchmark shards, per-package machine attribution and one run ID, missing/conflicting provenance rejection, spaced paths, stale-result replacement, and watchdog completion/expiry. Shell/workflow checks pass; no Conbench upload was performed locally. On total runner use: the last completed benchmark run before this follow-up totaled about 120.9 minutes across the six benchmark jobs, plus about 0.48 minute for setup/combine, with a 41.4-minute benchmark wall span. Those are elapsed job durations, not billed-minute accounting. That is below the previously cited 198–208-minute run, but sharding itself reduces wall time rather than eliminating aggregate work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
