Skip to content

fix(agentx): upgrade harness to 1.0.10 for SPAWN worker affinity - #4119

Merged
cquil11 merged 2 commits into
mainfrom
cam/agentx-1.0.10
Oct 15, 2026
Merged

cquil11 merged 2 commits into
mainfrom
cam/agentx-1.0.10

Conversation

@cquil11

@cquil11 cquil11 commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Upgrade the isolated AgentX benchmark dependency from agentx-harness==1.0.9 to 1.0.10 and update the standalone install guide. The release includes Anthony's SPAWN worker-affinity fix, preventing child sessions from accumulating duplicate state across client workers. Metric collection, calculations, and exports are unchanged.

Release: https://github.com/SemiAnalysisAI/agentx-harness/releases/tag/agentx-v1.0.10. Fix: SemiAnalysisAI/agentx-harness#52.

The fix-only c6656 AgentX run completed with zero profiling errors. Independent reconstruction from all 781,455 profiling records reproduced the core exported statistics and full inter-chunk distribution: https://github.com/SemiAnalysisAI/InferenceX/actions/runs/38683542278/job/116253300866.

The 1.0.10 release passed benchmark smoke tests from wheel and source installations on Python 3.11–3.13, then installed the published package from PyPI and passed the benchmark smoke test again: https://github.com/SemiAnalysisAI/agentx-harness/actions/runs/38764721499. The published worker-router code is byte-identical to the patch used in the c6656 run.

@cquil11
cquil11 requested a review from a team October 15, 2026 15:57
@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution!

  • Review: If this PR changes files owned by someone other than a repository admin or @SemiAnalysisAI/core, ask one eligible CODEOWNER to complete the latest PR_REVIEW_CHECKLIST.md before contacting a core maintainer on Slack. Follow the template exactly, including As a PR reviewer and CODEOWNER, I have reviewed this and have, so sign-off verification triggers.
  • PR verification: Sweeps run only when the PR appends an inferencex-e2e/perf-changelog.yaml entry and carries exactly one primary label: full-sweep-fail-fast (strongly recommended; canary plus per-matrix fail-fast), full-sweep-enabled (canary; matrix jobs continue after a failure), or non-canary-full-sweep-enabled (no canary or fail-fast). The modifiers all-evals, evals-only, and agentx-fast require a primary label. On fork PRs, a maintainer applies the label. See sweep labels and reuse.
  • After merging: PR authors must ensure all GitHub Actions jobs pass. Transient failures often pass on rerun; see how to rerun failed jobs.
中文

感谢你的贡献!

  • **审阅:**如果 PR 修改的文件归属于仓库管理员及 @SemiAnalysisAI/core 之外的 CODEOWNER,请先联系一位有资格的 CODEOWNER 填写最新的 PR_REVIEW_CHECKLIST.md,再通过 Slack 联系核心维护者。必须严格遵循模板,并保留 As a PR reviewer and CODEOWNER, I have reviewed this and have,才能触发签核验证。
  • **PR 验证:**只有当 PR 在 inferencex-e2e/perf-changelog.yaml 末尾追加了条目,并且恰好带有一个主标签时,才会运行扫描:full-sweep-fail-fast(强烈推荐;canary 加逐矩阵 fail-fast)、full-sweep-enabled(有 canary;矩阵任务在失败后继续运行)或 non-canary-full-sweep-enabled(无 canary,也无 fail-fast)。修饰标签 all-evals、evals-only 和 agentx-fast 必须与主标签一起使用。fork PR 的标签由维护者添加。参见扫描标签与复用。
  • **合并后:**PR 作者必须确保所有 GitHub Actions 任务通过。临时性失败通常可以通过重新运行恢复;参见重新运行失败任务的说明。

@github-actions

Copy link
Copy Markdown
Contributor

inferencex-e2e/infx diff: +1 -1

Generally most InferenceX submissions don't need to add changes to the infx package. On the off chance they do, generally the diff is small. Please prompt your agent to clean your PR to keep your diff to only necessary & minimal changes too. We have an increased code quality bar for changes to the infx package.

中文

大多数 InferenceX 提交通常不需要修改 infx 包。即使确实需要,改动通常也很小。请让你的 agent 清理 PR,使改动只包含必要且最小的内容。infx 包的改动有更高的代码质量要求。

@cquil11
cquil11 merged commit 8d9075e into main Oct 15, 2026
24 checks passed
@cquil11
cquil11 deleted the cam/agentx-1.0.10 branch October 15, 2026 15:59

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, straightforward dependency version bump with doc sync and a properly formatted changelog entry.

What was reviewed:

  • Version consistency: requirements.txt and the standalone doc both now pin agentx-harness 1.0.10, no stray 1.0.9 references left behind.
  • perf-changelog.yaml entry appended at the physical tail, English-only, correct schema fields.
  • Wildcard config-keys: ["*"] + scenario-type: agentic-coding scoping mirrors existing precedent for harness-wide pin bumps (e.g. the prior srt-slurm pin entry), so it's appropriately scoped rather than overly broad.
  • pr-link still shows the pull/XXX placeholder, but that matches CONTRIBUTING.md's own documented example and two pre-existing changelog entries use the same placeholder, so it isn't a new issue introduced by this PR.
Extended reasoning...

Three-file diff: a version bump from agentx-harness 1.0.9 to 1.0.10 in a doc and a requirements.txt, plus one appended perf-changelog.yaml entry; no code paths, auth, or data handling are touched. Verified the version bump is consistent across both files, the changelog append preserves prior bytes and lands at the physical tail, and the wildcard config-keys usage with scenario-type scoping has direct precedent elsewhere in the file for similar harness-level dependency bumps. The only minor wrinkle (pr-link placeholder pull/XXX) is a pre-existing, documented pattern in this repo rather than something unique to this change, so it doesn't warrant blocking.

This review covers commit e8928bc, which is no longer the latest commit on this pull request; later commits are not covered by it.

Jasen2201 added a commit that referenced this pull request Oct 15, 2026
…om-disagg-agentx

Resolve the perf-changelog conflict with #4065 and #4119 using
prepare_perf_changelog_merge resolve-conflict; this PR's entry stays the
tail append.

用 prepare_perf_changelog_merge resolve-conflict 解决与 #4065、#4119 的
perf-changelog 冲突,本 PR 的条目仍是末尾追加。

[skip-sweep]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant