Skip to content

Publish FastLanes retry archive metadata - #175

Closed
Anionix wants to merge 1 commit into
mainfrom
codex/publish-fastlanes-retry-evidence
Closed

Publish FastLanes retry archive metadata#175
Anionix wants to merge 1 commit into
mainfrom
codex/publish-fastlanes-retry-evidence

Conversation

@Anionix

@Anionix Anionix commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Summary

  • preserve the Linux retry environment, build command, per-case outcomes, and Release archive metadata in the pinned FastLanes research record
  • link the durable v0.1.0 archive and checksum sidecar from the research log
  • test that the workflow run, architecture, failure classification, and Release asset remain machine-readable

Verification

  • jq empty research/formats/fastlanes.json
  • git diff --check
  • nix develop --command ruff check src tests
  • nix develop --command pyright
  • nix develop --command uv run --frozen pytest -q

Closes the evidence gap left by #173; follows #172 as a fresh branch from origin/main. FastLanes remains PARTIAL/FAILED and excluded from rankings. Related: #38

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 75ad313943

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"runtime": "0.1.4"
},
"result": "numeric and all five string cases exited SIGSEGV; the mixed 13-column case raised RuntimeError UNREACHABLE; malformed comma input raised RuntimeError. The workflow preserved per-case inputs, artifacts, logs, and SHA-256 hashes."
"build_command": "nix develop --command python -m venv native/fastlanes/.venv; nix develop --command native/fastlanes/.venv/bin/python -m pip install scikit-build-core==0.11.6 cmake==4.4.0 ninja==1.13.0 pybind11==2.12.1 setuptools-scm==8.3.1; CMAKE_BUILD_PARALLEL_LEVEL=4 nix develop --command native/fastlanes/.venv/bin/python -m pip install --no-build-isolation -e native/fastlanes",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Record the build tools actually used

For anyone reproducing this retry, this command installs CMake 4.4.0 and Ninja 1.13.0 into the build virtualenv, while the adjacent environment record and new research-log claim identify CMake 4.1.2 and Ninja 1.13.2. The workflow obtained the latter versions by probing nix develop --command cmake/ninja, not the executables selected by the virtualenv's scikit-build-core invocation, so the published evidence is internally inconsistent about a potentially outcome-affecting part of the toolchain; record the effective build executables and distinguish them from the Nix-host versions.

Useful? React with 👍 / 👎.

@Anionix

Anionix commented Jul 16, 2026

Copy link
Copy Markdown
Owner Author

Superseded by merged PR #174, which persists the same Release asset SHA and host provenance on current main. No evidence is lost.

@Anionix Anionix closed this Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant