Skip to content

Stabilize Rosetta test timing and retry delay telemetry - #47832

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/fc573bfff912e999cf74b94a1c6e7ae1be07974b
Sep 24, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/fc573bfff912e999cf74b94a1c6e7ae1be07974b

Conversation

@copyberry

@copyberry copyberry Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Stabilize Rosetta test timing and retry delay telemetry

Why

Cold Rosetta translation and cache invalidation from hard-linked executables can interfere with timed CLI tests. Sampling the clock twice also makes local retry telemetry report a delay shorter than the selected backoff.

What changed

  • Warm CLI fixtures with --version on macOS x86_64 before timed checks, and use copies or Unix symlinks to avoid invalidating the shared executable's Rosetta cache.
  • Use one clock sample to calculate the response retry deadline and recorded delay.
  • Include the retry telemetry event in delay-range assertion failures for the headerless rate-limit stream test.

## Why

Cold Rosetta translation and cache invalidation from hard-linked executables can interfere with timed CLI tests. Sampling the clock twice also makes local retry telemetry report a delay shorter than the selected backoff.

## What changed

- Warm CLI fixtures with `--version` on macOS x86_64 before timed checks, and use copies or Unix symlinks to avoid invalidating the shared executable's Rosetta cache.
- Use one clock sample to calculate the response retry deadline and recorded delay.
- Include the retry telemetry event in delay-range assertion failures for the headerless rate-limit stream test.

GitOrigin-RevId: fc573bfff912e999cf74b94a1c6e7ae1be07974b
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/fc573bfff912e999cf74b94a1c6e7ae1be07974b branch from 676a089 to 282cd7b Compare September 24, 2026 13:10
@copyberry
copyberry Bot merged commit 282cd7b into main Sep 24, 2026
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/fc573bfff912e999cf74b94a1c6e7ae1be07974b branch September 24, 2026 13:10
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 24, 2026
@lattwood
lattwood deployed to issue-triage September 24, 2026 13:31 — with GitHub Actions Active
@lattwood
lattwood deployed to issue-triage September 24, 2026 13:31 — with GitHub Actions Active
@lattwood
lattwood deployed to issue-triage September 24, 2026 13:31 — with GitHub Actions Active
@lattwood
lattwood deployed to issue-triage September 24, 2026 13:32 — with GitHub Actions Active
@mrTyom
mrTyom deployed to issue-triage September 24, 2026 13:35 — with GitHub Actions Active
@mrTyom
mrTyom deployed to issue-triage September 24, 2026 13:35 — with GitHub Actions Active
@mrTyom
mrTyom deployed to issue-triage September 24, 2026 13:35 — with GitHub Actions Active
@mrTyom
mrTyom deployed to issue-triage September 24, 2026 13:37 — with GitHub Actions Active
@kumorig
kumorig deployed to issue-triage September 24, 2026 13:41 — with GitHub Actions Active
@kumorig
kumorig deployed to issue-triage September 24, 2026 13:41 — with GitHub Actions Active
@kumorig
kumorig deployed to issue-triage September 24, 2026 13:41 — with GitHub Actions Active
@kumorig
kumorig deployed to issue-triage September 24, 2026 13:43 — with GitHub Actions Active
@rivman
rivman deployed to issue-triage September 24, 2026 13:43 — with GitHub Actions Active
@rivman
rivman deployed to issue-triage September 24, 2026 13:43 — with GitHub Actions Active
@rivman
rivman deployed to issue-triage September 24, 2026 13:43 — with GitHub Actions Active
@bgubitosa
bgubitosa deployed to issue-triage September 24, 2026 13:50 — with GitHub Actions Active
@bgubitosa
bgubitosa deployed to issue-triage September 24, 2026 13:50 — with GitHub Actions Active
@bgubitosa
bgubitosa deployed to issue-triage September 24, 2026 13:50 — with GitHub Actions Active
@Lermont
Lermont deployed to issue-triage September 24, 2026 13:59 — with GitHub Actions Active
@Lermont
Lermont deployed to issue-triage September 24, 2026 13:59 — with GitHub Actions Active
@Lermont
Lermont deployed to issue-triage September 24, 2026 13:59 — with GitHub Actions Active
@Jackten
Jackten deployed to issue-triage September 24, 2026 14:00 — with GitHub Actions Active
@Jackten
Jackten deployed to issue-triage September 24, 2026 14:00 — with GitHub Actions Active
@Jackten
Jackten deployed to issue-triage September 24, 2026 14:00 — with GitHub Actions Active
@Lermont
Lermont deployed to issue-triage September 24, 2026 14:00 — with GitHub Actions Active
@Jackten
Jackten deployed to issue-triage September 24, 2026 14:01 — with GitHub Actions Active
@2c67cc18
2c67cc18 deployed to issue-triage September 24, 2026 14:04 — with GitHub Actions Active
@2c67cc18
2c67cc18 deployed to issue-triage September 24, 2026 14:04 — with GitHub Actions Active
@2c67cc18
2c67cc18 deployed to issue-triage September 24, 2026 14:04 — with GitHub Actions Active
@2c67cc18
2c67cc18 deployed to issue-triage September 24, 2026 14:05 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
issue-triage — 282cd7b0 Deployed Sep 24, 2026 by SjaakieChen via Identify potential duplicates (all issues) #48007
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.